Quote Originally Posted by Igor Vartanov View Post
Static an global variables are constructed long before any calls become functional on the loaded code. So your fiasco's possibility is imaginary only.
"The problem we're concerened with, involves at least to separately compiled source files, each of which contains at least one non local static object (i.e an object that's global, namespace scope or static in a class or at file scope). And the actual problem is this : if initialzation of a non-local static object in one translation unit uses a non-local static object in a different translation unit, the object it uses could be uninitialized." [Meyers]