Re: [boost] [thread] Proposal for thread safe initialization of local static and global objects

Anthony Williams wrote:

The MSVC compiler will schedule a call for each static object, so they are destroyed in the correct reverse order, and correctly interleaved with other calls to atexit, as per 3.6.3p3 of the C++ Standard.

Strictly speaking we do not have static objects but dynamically created objects on the heap. So we simply cannot be not conformant to the standard. But I think your intent is: since we make the object appear like they are static, they should behave similar to real static objects. Correct? Roland