Coding standards: Function name aliases: how to use?

[vocx]

you still didn't justify what the purpose of all this work is...

What is the purpose of standards? Did you think about that before?

Standards help everybody get on the same path. That's the purpose of this. Development occurs better and with less errors when people follow standards.

[Zolko]

.... and ask for a little de-escalation in the tone of this important exchange of ideas and long term vision.

While I agree with you on general terms, how am I supposed to react to :

You aren't thinking long term.

Did you think about that before?

I'm honestly interested in how a (this) community is answering a clearly abusing clueless moron ? Now, as a moderator, you'll have to make decisions. Please don't forget the open/free source mantra of: show me the code. This is the only thing that counts.

[Cyril]

Not a proof but an example. Blender is coded mainly in C, some libraries are in C++ and all the python API is PEP8 compliant. I found so much easier to get into Blender Python API than FreeCAD Python API. Of course PEP8 is not the only reason (UI is easy to modify, class inheritance etc…). It is clean and easy to read and get into.
Edit : Also if you look at old Blender Python API you will see that it was absolutely not the case before : API 2.25. So they did this work. Maybe we could found some discussions about it but I am pretty sure that you will find the same kind of pro/cons .

About keeping C++ style it could eventually make sense if you use mainly exactly the same class and function in both languages like it is in PySide2 (or Revit… cause it is all .NET and API is the same for C++/VB.NET/C#/python/Ruby and any .NET compatible language) but it is not the case for FreeCAD. API is not the same in C++ and python for many things.

[Kunda1]

Not a proof but an example. Blender is coded mainly in C, some libraries are in C++ and all the python API is PEP8 compliant. I found so much easier to get into Blender Python API than FreeCAD Python API. Of course PEP8 is not the only reason (UI is easy to modify, class inheritance etc…). It is clean and easy to read and get into.
Edit : Also if you look at old Blender Python API you will see that it was absolutely not the case before : API 2.25. So they did this work. Maybe we could found some discussions about it but I am pretty sure that you will find the same kind of pro/cons .

About keeping C++ style it could eventually make sense if you use mainly exactly the same class and function in both languages like it is in PySide2 (or Revit… cause it is all .NET and API is the same for C++/VB.NET/C#/python/Ruby and any .NET compatible language) but it is not the case for FreeCAD. API is not the same in C++ and python for many things.

This post is a breath of fresh air. Thank you for the insight @Cyril

[vocx]

...Blender is coded mainly in C, some libraries are in C++ and all the python API is PEP8 compliant. I found so much easier to get into Blender Python API than FreeCAD Python API.
...

Exactly my point. Blender has a great API because over the years they have done the work to standardize and place things into submodules. It's hard work, but somebody has to do it if, in the future, you want to have clean and maintainable structures.

Despite the age of FreeCAD (18 years), we are barely getting things into a better shape. A lot of work is still needed.