Frank Swarbrick wrote:
Now imagine that the DLL gets loaded repeatedly and in each case only one of
the programs it contains is actually executed. That case could have
performance problems in the C world because the static data for all of the few
thousand independent programs is created and initialized for each load of the
DLL (and in each case you're only running one of the programs.)
That isn't typically the design pattern for DLL's, "thousands of independent
programs".
Further, the static area is unloaded when the instance that invoked the DLL exits but the DLL itself stays loaded until
the last instance using it exits.
--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
