Static variable lifetimes, file-scope vs. function scope

Question

suppose I have a .cpp file:

static Foo aFoo;

Foo& staticFoo(){
    return aFoo; 
}

Foo& singletonFoo(){ // not thread safe in c++-03
    static Foo staticFoo;
    return staticFoo;
}

and a .h file that exposes these functions (but not aFoo directly).

Am I certain that aFoo is initialized prior to staticFoo?
Am I certain that staticFoo is destroyed after aFoo?
Am I certain that aFoo is destroyed after any automatic storage duration variables in my program?

@ecatmur Because C++98 doesn't guarantee static local initialization to be thread safe (since it doesn't mention threads at all). — Mark B
– Mark B, Commented Feb 24, 2015 at 16:29

Mark B · Accepted Answer · 2015-02-24 16:43:44Z

2

No. If someone calls singletonFoo from another translation unit during static initialization then it's unspecified.
No because the destruction happens in reverse order of construction and we already established that construction is not guaranteed.
aFoo will be destroyed after all local/automatic variables.

edited Feb 24, 2015 at 16:43

answered Feb 24, 2015 at 16:28

Mark B

96.5k10 gold badges113 silver badges198 bronze badges

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

1 Comment

Dave Over a year ago

non-static means "not declared with static", i.e. automatic storage duration variables.

Collectives™ on Stack Overflow

Static variable lifetimes, file-scope vs. function scope

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related