C++ house naming convention

[mindhells]

There're different naming conventions in use in the C++ layer of Gnofract4D.
Some examples on user-defined types:

• MTFractWorker, IImage ...
• s_pixel_stat, s_rgba, s_pf_data ...
• fractFunc, pointFunc ...
• image_reader, image_writer ...

on members:

• nThreads ...
• m_totalXres, m_totalYres ...
• auto_deepen ...
• lookup_with_transfer() ...
• totalXres(), getBuffer() ...

which would be the ones to pick for new code or to normalize the existing?

Check this reference

[edyoung]

As you've noticed, the naming style is quite inconsistent today, I guess because I have never been that religious about it. In general I would be happy to see more or less any consistent coding style adopted.

Ideally:

• We adopt one off the shelf rather than defining one
• it would be one where there was some tooling available to point out inconsistencies
• any changes to update areas of code to conform to style would only do that, not mixed in with other changes, even refactoring - makes code review much easier.

https://clang.llvm.org/extra/clang-tidy/ might be worth a look