Initialize global variable before any other global variables

I need to initiate a global variable to a class before the
initialization of any other global variable.
The problem is that when I link the application with a dll, some or
all global variables in the dll is initialized before mine.

Is there a way to ensure that my global variable is initialized before
any other?

Take a simple class

class test {

}

#pragma init_seg(compiler)
test t;

According to msdn, "Objects in this group are constructed first".
That's the "compiler" group.

I'm using Microsoft Visual Studio.net 2005/VC++ on Windows XP

jubelbrus wrote:Well... Search the FAQ for "fiasco". Draw your own conclusions.
There is no such thing in standard C++ language. It's something that
most likely unique to that compiler.
Then you need to ask in the newsgroup dedicated to that compiler.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask

On Jul 18, 1:59 pm, jubelbrus <thomas.heggel...@gmail.comwrote:Why? Check out the singleton idiom. It can't guarantee this,
but it usually guarantees enough---that the variable is
initialized before it is used.

--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

"James Kanze" <james.kanze@gmail.comwrote in message
news:1184855301.343186.294920@z24g2000prh.googlegr oups.com...
On Jul 18, 1:59 pm, jubelbrus <thomas.heggel...@gmail.comwrote:"Why? Check out the singleton idiom. It can't guarantee this,
but it usually guarantees enough---that the variable is
initialized before it is used."

The trickier issue is making sure it sticks around long enough after main
because chances are, that if it needs to be used by other globals before
main that it will be used after main also.

John

On Jul 20, 12:19 am, "JohnQ" <johnqREMOVETHISprogram...@yahoo.com>
wrote:In practice, that's less often a problem; destructors generally
don't need nearly as much as constructors. And in the classical
Singleton idiom (in the GoF), the singleton object is never
destructed anyway. (My generic singleton offers the choice, but
defaults to never destructing, since that is the prefered
behavior 99% of the time.)

--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34