Google C++ style guide : something every C++ coder out there should read or ““Within C++, there is a much smaller and cleaner language struggling to get out.”

Having over 100 million lines of C++ code, google took the C++ problem (language with so many features, different ways of doing the same things, dangerous constructs, some pointers to the problems with c++ can be found on wikipedia, and here for an authoritative opinion) seriously and this is what came out.

Some interesting decisions taken :

“We do not use C++ exceptions.” from here

“Avoid defining macros, especially in headers; prefer inline functions, enums, and const variables. Name macros with a project-specific prefix. Do not use macros to define pieces of a C++ API.” from here.

“Avoid complicated template programming” from here

“Within C++, there is a much smaller and cleaner language struggling to get out.” — Bjarne Stroustrup

Paul Stephen Borile

software teams management, golang/c coding, bass player, biking addicted

Google C++ style guide : something every C++ coder out there should read or ““Within C++, there is a much smaller and cleaner language struggling to get out.” — Bjarne Stroustrup”