In this thread I'd like to discuss all coding conventions of the ott3d branch.
Specifically, I'd like to settle on a coding style. Currently, styles are being mixed, which is something that drives me
I was able to count three different naming conventions:
Code: Select all
// 1:
void autofit_tracks();
// 2:
bool handle_Window_mouseEnter(const CEGUI::EventArgs &e);
// 3:
void updateLightmap();
Code: Select all
void someFunction(); // Function
int someVariable; // Variable
Entity* someEntity; // Pointer
class SomeClass{
private:
int mSomeAttribute; // Member variable = attribute
Entity* mSomeEntity; // Member pointer
public:
void someMethod(int someArgument, int anotherArgument); // Member function = method
void aMethodWithLongName();
}
And finally, even naming the source files should follow some rule. Doesn't matter which it is, but it should be consistent.
~An00biS