   C++ namespace nameing convention
  I was just curious what nameing conventions people use when naming their namespaces. I've seen:- namespace foo_space- namespace _foo_space- namespace FooSpace- namespace _FooSpaceWhich do you prefer or do you use a different nameing convention all together? The reason why I ask is because I want my code to be as readable as possible and stick to the nameing convention that the majority of people are use to seeing. Thanks.   
  "stick to the nameing convention that the majority of people are use to seeing"Well what nameing convection are you using? You should be consistant, so that if you are using hungerian then don't use "_"   ;  Whatever you do, don't use the last one.  Identifiers starting with an underscore followed by a capital letter are reserved for compiler and standard library writers for use at any scope.Σnigma   ;  I'd also avoid the second one as names beginning with an underscore usually indicate "not to be touched" (at least to me - I personally use a boost-like "detail" namespace for internals). The first and third are both common - the first is used in boost and C++ STL and is advocated by the GNU coding standards, but the second is used by Microsoft for all its libraries (as far as I know) and is the standard Java naming system. Take your pick.   ;  There is not much benefit to encoding information into the name of a namespace, so I just use the same form I use for all the other symbols types that have scope: FooSpace.   ;  Thanks for the reminder about the microsoft lib nameing convention. I completely forgot about that.;foospace I always name the namespace after a group and I never found a use of adding "spaces" to a name. I don't really use namespaces that often. The only one I ever used is the name of the engine(lunarlady) and math).   ;  I try to keep them as few letters as possible, that way I feel like I have less need to put a "using namespace..." at the top of my code to save my typing out a lot every once in a while. 4 or less letters, lower case, I try to abide by that.   ;Quote:Original post by JohnBoltonThere is not much benefit to encoding information into the name of a namespace, so I just use the same form I use for all the other symbols types that have scope: FooSpace.QFE.