Wrong static initialization order

[Sandro Bosio]

Hello everybody, my first message on this forum. I tried to solve my issue by reading other similar posts, but I didn't succeed. And forgive me if this mail is so long.

I'm trying to achieve the following (with incomplete succes): I want in a given namespace Parameters a list of "initialize rs" (which are objects derived from a simple interface that can be implemented anywhere, and are used to define which parameters the program will take at command line) to be registered before the main starts, or better, before a function parse(argv, argc) of the namespace Parameters is called (from the main). The goal is that I to have such initializers to be called in some automatic way.

The working solution:

Each initializer is a static variable (placed in the file to which the initializer belongs) derived form a virtual class "ParametersInit ializer", and its constructor calls a function Parameters::reg isterInitialize r() passing its own pointer. Inside registerInitial izer I keep track of the pointers inside a simple linked list, by storing its head and tail as static variables inside Parameters.cpp. When calling parse(), and hence when every initialization went right (especially the std::map I use to store the parameters) I call some function for each registered initializer which adds the parameters.

Now, what I want is to use an object for this list. It does not work neither with std::list nor with a very simple list object I wrote. The problem seems to be the order of initialization of static variables, which I know is not defined between different files. But I assumed that whenever a static variable is accessed, it must had been previously initialized. Which seems not to be the case.

I tried to condensed my problem in the following files:

/********************************************************************/
Parameters.h
/********************************************************************/
#ifndef PARAMETERS_H
#define PARAMETERS_H
 
// This is the prototype for the Initializers to be stored at creation time
// and, later on, used by parse()
class ParametersInitializer {
public:
        ParametersInitializer();
        virtual ~ParametersInitializer();
};
 
// Namespace for parameter parsing
namespace Parameters {
        // Function for registering initializers in the list
        void registerInitializer(ParametersInitializer * aInitializer);
 
        // Command line parser
        void  parse(int argc, char ** argv);
};
 
#endif
 
/********************************************************************/
Parameters.cpp
/********************************************************************/
#include <iostream>
#include "Parameters.h"
#include "PointerList.h"
 
// List of the initializers
static PointerList Initializers;
 
ParametersInitializer::ParametersInitializer()
{
        // I would like to register here, but then it will acces virtual function
        // Parameters::registerInitializer(this);
}
 
ParametersInitializer::~ParametersInitializer()
{
}
 
void Parameters::registerInitializer(ParametersInitializer * aInitializer)
{
        // Registers the initializer in the static PointerList object
        Initializers.store((void *) aInitializer);
        cout << "Registering. Now there are " << Initializers.size() << " registered Initializers" << endl;
}
 
void Parameters::parse(int argc, char ** argv)
{
        cout << "Parsing..." << endl;
        // Prints the number of registered initializers
        cout << "There are " << Initializers.size() << " registered Initializers" << endl;
 
        // Does the parsing of argc argv, code omitted
}
 
/********************************************************************/
PointerList.h
/********************************************************************/
#ifndef POINTERLIST_H
#define POINTERLIST_H
 
#include <iostream>
using namespace std;
 
// This should store pointers in a linked list
// In this example just stores the size of such list
 
class PointerList{
public:
        PointerList() : count(0)
        {
                cout << "Creating a PointerList object" << endl;
        }
 
        void store(void * pointer)
        {
                count++;
        }
 
        int size()
        {
                return count;
        }
private:
        int count;
};
 
#endif
 
/********************************************************************/
somefile.cpp
/********************************************************************/
#include <iostream>
#include "Parameters.h"
 
using namespace std;
 
// Derives from ParametersInitializer
class Initializer_B : public ParametersInitializer {
public:
        Initializer_B()
        {
                cout << "Creating an object of type Initializer_B" << endl;
                Parameters::registerInitializer(this);
        }
};
 
// Three static variables, for which the constructor will be called
static Initializer_B tmp1;
static Initializer_B tmp2;
static Initializer_B tmp3;
 
/********************************************************************/
main.cpp
/********************************************************************/
#include <iostream>
#include "Parameters.h"
 
using namespace std;
 
// Derives from ParametersInitializer
class Initializer_A : public ParametersInitializer {
public:
        Initializer_A()
        {
                cout << "Creating an object of type Initializer_A" << endl;
                Parameters::registerInitializer(this);
        }
};
 
// Static variable, for which the constructor will be called
static Initializer_A tmp1;
static Initializer_A tmp2;
 
// Main function
int main(int argc, char ** argv)
{
        // Parses arguments
        Parameters::parse(argc, argv);
 
        return EXIT_SUCCESS;
}
 

As you notice, in this example there are 5 static initializers: two of type Initializer_A in main.cpp and three of type Initializer_B in somefile.cpp (obviously there should be just one static variable for each derived initializer, this is just an example).

Now, if I compile these files (the compiler is gcc version 4.0.1 for Mac) and run the program, I obtain the following output:

Creating an object of type Initializer_B
Registering. Now there are 1 registered Initializers
Creating an object of type Initializer_B
Registering. Now there are 2 registered Initializers
Creating an object of type Initializer_B
Registering. Now there are 3 registered Initializers
Creating a PointerList object
Creating an object of type Initializer_A
Registering. Now there are 1 registered Initializers
Creating an object of type Initializer_A
Registering. Now there are 2 registered Initializers
Parsing...
There are 2 registered Initializers

As you can see, first the three Initializer_B static objects are created, then the static object PointerList, and finally the two Initializer_A static objects. And therefore three initializers are lost. Obviously you may have different outcomes, since the order is undefined. But I expected PointerList to be the first, since both Initializer_A and Initializer_B access the static object PointerList (from register()).

Is gcc's fault? Or is the order undefined nomatter which object access whichother? I know that the order of initialization is unspecified among different files, but I assumed that if static A uses static B, then static B will be initialized first (or in other words, that when a static object is accessed it have been already initialized).

How can I make all this working? Is the only option to manage such a list by simple static variables (with constant initializers) and directly from within Parameters.cpp?

Anoter (smaller) problem is that I have to call the function "registerInitia lizer" from the constructor of each derived class, because if I call it from the constructor of the base class "ParametersInit ializer" (which would be a much cleaner solution), then when I access the pure virtual function he does not access those of the derived class, but the virtual ones (with a runtime errror). Any way out?

Thanks and sorry again for the long mail,
Sandro Bosio

[Sandro Bosio]

This is an update on my own message.

First forget about the fact that I cannot register the initializer from the constructor of the base class ParametersIniti alizer. Indeed now I do, I don't know why I had problems with virtual functions before (but I had them), now they seem to have disappeared.

I found out that having the PointerList object as a static member of ParametersIniti alizer partially solves the issue. Doing so and compiling the files, one obtains the proper initialization order (which is PointerList first), probably because the compiler finds out that such a order is needed (while before the need for initialization was hidden in a call to a function).

However, the problem still remains. When Parameters.cpp is compiled in a library, which is then linked when compiling main.cpp and somefile.cpp, then again the initialization order can fail (it happens to me at least). So, the question is still valid. Can I assume that whenever I access a static object it has been previously initialized, or I cannot?

However, I found a satisfying solution, which is having as static variable a pointer to a list (std::list or any other implementation) , with a constant initialization NULL, and creating the list when at the first call of registerInitial izer().

Best,
Sandro