Quote:
Exactly, but static member variables at least aren't exactly orphans, no need to redeclare them as extern in whatever source file you need access to them, and they move along with the class definition in case of code reuse.
I guess its a matter of practical evilness vs technical evilness? usability vs concept?
No. They're just not solutions. Who cares if they move with the class, or are "orphans" -- what's an orphan? A static variable is basically a global in a namespace, plus some other language-related fluff and constraint, nothing special. They have the same problems. If static variables exhibit the same deep-rooted problem that globals have, how can you consider them a "solution" in any sense of the word?
They just have slightly different implementation flavor.
