-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Elisha Berns Sent: Monday, August 29, 2005 4:17 PM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Boost.Thread memory leak reported

Peter Dimov wrote:

...

C++ doesn't guarantee a particular initialization order for file scope objects in different translation units, so we have to resort to local statics or call_once.

I hear you, I hear the point. I don't have a good solution to this, but I hope someone does!

What about having a single singleton solely responsible for initializing all the other ones?