Hacking conventions

Rough draft taken from the blog, not to forget about it:

Here are the vital hacking rules:

• Follow the camel casing already used in the code. (aka Cameleon coding)

_private member

variable_name

FunctionName()

ect...

• Ask before working on new features, you might be frustrated if it's not accepted after all the time you've spent on them. You'll be warned. ;)
• Tabs are accepted for now, but will have to be changed to use 4 spaces instead somewhere in the future.
• Never use: using namespace std; in new file, and remove them if you have the patience, since it's a very bad practice and is bad for the compile time.
• Never use: the defs.h file, use class x; ect at the beginning of your include file instead. The defs.h file is bad for compile time, and bad for the unlinking of the editor and the engine for instance, and last but no least, it shall perish somewhere in the future.
• Never include the big video.h if you can only include image.h, for instance.