[boost] Is there any interest in a base class which prevents construction during the static initialization phase?

12 Jun 2011

      Hello,

Because the order of static initialization is undefined, numerous difficult
to detect problems can arise when multiple objects are initialized during
the static initialization phase.  This base class would guarantee that a
class will never be unintentionally constructed during static
initialization.  This is the same philosophy behind how boost::noncopyable
guarantees that a class will never be unintentionally copied.

Usage would appear as follows:

#include <submission/nonstaticinitializable.hpp>
#include <boost/noncopyable.hpp>

namespace
{
    class Foo : private submission::nonstaticinitializable, private
boost::noncopyable
    {
    public:
        Foo() : nonstaticinitializable() {}
    };   // Foo

}   // unnamed namespace

Foo fooThatWillAssert; // This instance asserts during static initialization

int main()
{
    nonstaticinitializable::enable_initialization(); // Indicates that
static initialization is complete.
    Foo foo; // This instance initializes successfully after static
initialization.
    return 0;
}   // main

What does Boost think about submission::nonstaticinitializable (I chose the
name to mirror noncopyable)?

Thank you,

Ben Robinson