What are the coding rules?
If you are creating a patch for Irrlicht and want it to be merged with the development branch, please try to follow these few rules: • Don’t add dependencies to other libraries or at least only if really, really necessary. • Don’t use the STL, use the Irrlicht built in containers instead. • Don’t use platform specific functions, use the internal os:: namespace for that if there is no other way to do what you need. • Always keep in mind that Irrlicht must be compileable on lots of different platforms and with several compilers. • Don’t use special compiler extensions and try to adhere to standard C++. • Use the Irrlicht types like f32 and u32 defined in irrTypes.h. • Try not to break the existing interface if it is not really necessary. Only change current behaviour of the engine if necessary. People should be able to upgrade to new Irrlicht engine versions as easily as possible. If you are doing this anyway, it would be a good idea to discuss this with niko before. • Try to adhere to t
