Re: static variables and dll/lib troubles

You are right. See my follow up post with my understanding of the issue.

The reason I have to do it this way is as follows. The library I use has a
Factory class that stores function pointers of each other class' creation
function. The Factory invokes the function pointer as necessary to create
any
class.

However, each creation function accepts no parameter or only string based
parameter. When I made a new class that requires a callback function
pointer
parameter upon creation, rather than breaking the pattern established by
the
Factory, I chose to pass the function pointer to the mentioned global
variable. This is then acquired by my new class upon creation.

Specifically, the parameter to my new class is a callback function pointer
as opposed to the int* in my example.