What is a good naming convention for vars, methods, etc in C++? [closed]

Question

I come from a the Objective-C and Cocoa world where there are lots of conventions and many people will say it makes your code beautiful! Now programming in C++ I cannot find a good document like this one for C++.

http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CodingGuidelines/CodingGuidelines.html

Standard C++ probably does not have something like above but I hope I can stick to some other SDK or APIs (like Microsoft's(?),etc) conventions.

I hope you can provide me with some links.

Answer 1

Do whatever you want as long as its minimal, consistent, and doesn't break any rules.

Personally, I find the Boost style easiest; it matches the standard library (giving a uniform look to code) and is simple. I personally tack on m and p prefixes to members and parameters, respectively, giving:

#ifndef NAMESPACE_NAMES_THEN_PRIMARY_CLASS_OR_FUNCTION_THEN_HPP #define NAMESPACE_NAMES_THEN_PRIMARY_CLASS_OR_FUNCTION_THEN_HPP  #include <boost/headers/go/first> #include <boost/in_alphabetical/order> #include <then_standard_headers> #include <in_alphabetical_order>  #include "then/any/detail/headers" #include "in/alphabetical/order" #include "then/any/remaining/headers/in" // (you'll never guess) #include "alphabetical/order/duh"  #define NAMESPACE_NAMES_THEN_MACRO_NAME(pMacroNames) ARE_ALL_CAPS  namespace lowercase_identifers {     class separated_by_underscores     {     public:         void because_underscores_are() const         {             volatile int mostLikeSpaces = 0; // but local names are condensed              while (!mostLikeSpaces)                 single_statements(); // don't need braces              for (size_t i = 0; i < 100; ++i)             {                 but_multiple(i);                 statements_do();             }                      }          const complex_type& value() const         {             return mValue; // no conflict with value here         }          void value(const complex_type& pValue)         {             mValue = pValue ; // or here         }      protected:         // the more public it is, the more important it is,         // so order: public on top, then protected then private          template <typename Template, typename Parameters>         void are_upper_camel_case()         {             // gman was here                         }      private:         complex_type mValue;     }; }  #endif 

That. (And like I've said in comments, do not adopt the Google Style Guide for your code, unless it's for something as inconsequential as naming convention.)