Subject: [boost] a new library Global Object Manager submission interest check
From: George Georgiev (george.georgiev.sf_at_[hidden])
Date: 2014-06-07 18:28:21
I have code that deals with problems related to initialization of global
1. Multi-threading - problems occurring in some singleton patterns based on
the fact that local for a function or method static variables are not
initialized in a thread safe manner
2. Initialization order - there is no multi-platform/multi-compiler
standard way to control the global objects initialization order
3. Static linking of global objects code without need - some patterns
result in global objects to be linked in the final executable, even if they
are provided from static libraries and the code that uses them is not in use
4. Capability for easy replacement of a global implementation object with a
I was struggling with shutdown issues in complex c++ application for years
in several different projects. With the solution I come up a few years ago
I have no issues in any project I have used it.
Please let me know if this is something of interest to the boost community.
Note that the boost singleton pattern used for path_locale (boost
filesystem path) is having the multi-thread issue I mentioned in point 1.
This is a small test that demonstrates the problem:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk