C/C++ naming conventions for variables: some_variable vs somevariable

Question

I am wondering what is actually the preferred way of naming variables: some_variable or somevariable. Looking at some libraries, I have seen both. What is more, some wide-spread style conventions like Google C++ Style Guide allow both.

What do you prefer and why? Is there a rule or good practice which tells when to use which? And does the same applies to argument names in functions/methods?

And is mixing those two conventions a good idea? If yes, when should the first naming conventions be used, and when the second one?

You forgot _PascalCase_ and _camelCase_. :) Also, this question is subjective (as is this comment). — Martin Hennings, Mar 30 '11 at 13:15
http://stackoverflow.com/questions/3706379/what-is-a-good-naming-convention-for-vars-methods-etc-in-c — Tyler, May 09 '16 at 22:30

score 0 · Answer 1 · answered Mar 30 '11 at 13:15

0

Use what's most readable and least confusing.

answered Mar 30 '11 at 13:15

Martin Hennings

16,418
9
48
68

score 0 · Answer 2 · answered Mar 30 '11 at 13:16

0

You should follow whatever naming convention makes sense to you.

For me, I always use camelCase for variables and PascalCase for public methods and properties.

answered Mar 30 '11 at 13:16

DNR

956
6
10

score 0 · Answer 3 · answered Mar 30 '11 at 13:30

The C++ standard libraries use both conventions for function and class names, though the _ convention is apparently gaining popularity (it's used in most recent additions, since the STL got standardized). Stick with your project guidelines, or make up your own, but apply them consistently.

My personal style is to use some_function for functions, somevar for variables, PascalCase for class names. I don't have a copy of The C++ Programming Language by Stroustrup around, but I believe this is his style as well.

C/C++ naming conventions for variables: some_variable vs somevariable

3 Answers3