10

I know that as of the C++03 standard, function-scope static initializations are not guaranteed to be thread safe:

void moo() { static std::string cat("argent"); // not thread safe ... } 

With the C++0x standard finally providing standard thread support, are function-scope static initializations required to be thread safe?

4
  • 3
    I think as of today it will be called C++1x Commented Jan 1, 2010 at 2:29
  • Bjarne Stoustrup says to think of the x as a hexidecimal number, so still 0x Commented Jan 1, 2010 at 5:29
  • @John: Regardless of what he may think or like, my understanding is that ISO guidelines require versioning of documents such as standards to be in base-10. Commented Jan 1, 2010 at 10:37
  • 5
    ISO guidelines have nothing to do with it, as C++0x isn't the formal name of the standard. Never was, never will be. And the same goes for C++1x. It's not an ISO name, so ISO's rules don't matter. Commented Jan 1, 2010 at 15:12

1 Answer 1

9

it seems the initialization would be thread safe, since in the case the object is dynamically initialized upon entering the function, it's guaranteed to be executed in a critical section:

§ 6.7 stmt.decl

4. ...such an object is initialized the first time control passes through its declaration... If control enters the declaration concurrently while the object is being initialized, the concurrent execution shall wait for completion of the initialization...

there is a potential edge-case, if after returning from main(), the destructor of a static object calls the function after the static local has already destroyed, the behavior is undefined. however, that should be easy to avoid.

Sign up to request clarification or add additional context in comments.

1 Comment

Famous last words "should be easy to avoid". It is tremendously difficult to avoid in the general case.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.