RF.rules: Coding rules

• Boost Library Requirements and Guidelines. ???.
• Bloomberg: BDE C++ Coding. Has a strong emphasis on code organization and layout.
• Facebook: ???
• GCC Coding Conventions. C++03 and (reasonably) a bit backwards looking.
• Google C++ Style Guide. Geared toward C++03 and (also) older code bases. Google experts are now actively collaborating here on helping to improve these Guidelines, and hopefully to merge efforts so these can be a modern common set they could also recommend.
• JSF++: JOINT STRIKE FIGHTER AIR VEHICLE C++ CODING STANDARDS. Document Number 2RDU00001 Rev C. December 2005. For flight control software. For hard real time. This means that it is necessarily very restrictive ("if the program fails somebody dies"). For example, no free store allocation or deallocation may occur after the plane takes off (no memory overflow and no fragmentation allowed). No exception may be used (because there was no available tool for guaranteeing that an exception would be handled within a fixed short time). Libraries used have to have been approved for mission critical applications. Any similarities to this set of guidelines are unsurprising because Bjarne Stroustrup was an author of JSF++. Recommended, but note its very specific focus.
• Mozilla Portability Guide. As the name indicates, this aims for portability across many (old) compilers. As such, it is restrictive.
• Geosoft.no: C++ Programming Style Guidelines. ???.
• Possibility.com: C++ Coding Standard. ???.
• SEI CERT: Secure C++ Coding Standard. A very nicely done set of rules (with examples and rationales) done for security-sensitive code. Many of their rules apply generally.
• High Integrity C++ Coding Standard.
• llvm. Somewhat brief, pre-C++11, and (not unreasonably) adjusted to its domain.
• ???