C++ static destructor guaranteed to be called?

M

Mike Schilling

Roedy Green said:
But DLLs can hang around for a long time after the app closes right?
So how does that work?

In Windows 3.x, DLLs owned resources and memory themselves, so what you
describe was an issue. In 32-bit Windows, resource ownership is (more
sensibly) per-process, and loading/unloading means "into a process's address
space", so the fact that the same DLL may be in use by another process is
unimportant.
 
R

Roedy Green

In Windows 3.x, DLLs owned resources and memory themselves, so what you
describe was an issue. In 32-bit Windows, resource ownership is (more
sensibly) per-process, and loading/unloading means "into a process's address
space", so the fact that the same DLL may be in use by another process is
unimportant.

Thanks. I did not know they had dropped the common data area.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,483
Members
44,901
Latest member
Noble71S45

Latest Threads

Top