Putting class static members definition into cpp file — technical limitation?

Question

one of my \"favorite\" annoyance when coding in C++ is declaring some static variable in my class and then looking at compilation error about unresolved static variable (in

Answer 1

First, from compiler's point of view, this is perfectly reasonable. Why redundant keyword where it is not needed?

Second, I'd recommend against static members in C++. Before everybody jumps, I will try to explain.

Well, you are not going to have any public static data members (very rarely useful). In any case, most classes have their own CPP file. If so, a static global, IMO is preferable over a private static member for reasons of dependency reduction. Unlike non-static private data, the static ones are not part of the interface, and there's very little reason why should the user of the h file ever have to recompile, or at all see these members.