Re: Threadsafe singletons

Fundamentally, it is almost the same issue here. The problem is
a compiler generated bool, which you, as the user, don't have
access to. It's not quite the same thing as the static
variables involved in, say, the stack walkback of exception
handling, but there is a basic principle involved. If I write:

    void
    f()
    {
        static int const xxx = 42 ;
        // ...
    }

no locking is required by the user. So I would expect the same
to hold for:

    void
    f()
    {
        static std::string const xxx( "doh" ) ;
        // ...
    }

--