Here are two C++ style habits that I recommend. Neither is earth-shattering, but both have a benefit that I find useful. Both relate to the order in which constness shows up in your syntax.
1. When you write a conditional, consider putting the constant (unchangeable) value first:
if (0 == i)
… instead of:
if (i == 0)
The reason is simple. If you forget/mis-type and accidentally write a single
= instead of two, making the expression into an assignment, you’ll get a compile error, instead of subtle and difficult-to-find misbehavior. (Thanks to my friend Doug for reminding me about this one not long ago.)
2. With any data types that involve pointers, prefer putting the
const keyword after the item that it modifies:
char const * VERSION = "2.5";
… instead of:
const char * VERSION = "2.5";
This rule is simple to follow, and it makes semantics about constness crystal clear. It lets you read data types backwards (from right to left) to get their semantics in plain English, which helps uncover careless errors. In either of the declarations of VERSION given above, the coder probably intends to create a constant, but that’s not what his code says. The semantics of the two are identical, as far as a compiler is concerned, but the first variant makes the mistake obvious. Reading right-to-left, the data type of VERSION is “pointer to const char” — so VERSION could be incremented or reassigned.
Use the right-to-left rule in reverse to solve the problem. If we want a “const pointer to const char”, then we want:
char const * const VERSION = "2.5";
That is a true string literal constant in C++. (Thanks to my friend Julie for teaching me this one.)
This might seem like nit-picky stuff, but if you ever get into const_iterator classes and STL containers, this particular habit helps you write or use templates with much greater comfort. It also helps if you have pointers to pointers and the like. (For consistency, I prefer to follow the same convention for reference variables as well. However, this is not especially important, since references are inherently immutable and therefore never bind to
Share a tip of your own, or tell me why you prefer different conventions.