<div>
but WHY the state data of each module is not application-wide?<br />

</div>


but WHY the state data of each module is not application-wide?


<div>
<div class="content wysiwyg-content">
Will someone please explain how &quot;Module state&quot; is maintained<br />
differently when using a USRDLL vs an AFXDLL? For example,<br />
for a USRDLL, when an CWinApp's InitInstance is called,<br />
the runtime automatically switches the state, but when I<br />
use the shared MFC DLL, I must call AFX_MAINTAIN_STATE(...)<br />
at the beginning of all exported functions.<br />
<br />
I don't really understand what is going on with the state, especially when multithreading comes into the picture.<br />
For example, if in an USRDLL I call AfxBeginThread and I'm<br />
linking to shared MFC DLL, how does module state come into play?
</div>
</div>


Will someone please explain how "Module state" is maintained
differently when using a USRDLL vs an AFXDLL? For example,
for a USRDLL, when an CWinApp's InitInstance is called,
the runtime automatically switches the state, but when I
use the shared MFC DLL, I must call AFX_MAINTAIN_STATE(...)
at the beginning of all exported functions.

I don't really understand what is going on with the state, especially when multithreading comes into the picture.
For example, if in an USRDLL I call AfxBeginThread and I'm
linking to shared MFC DLL, how does module state come into play?

AFX_MODULE_STATE with USRDLL vs AFXDLLs

Kernel and system programming is the process of creating the software necessary for a computer or device to function and operate other programs. Some operating systems (such as Microsoft Windows) are proprietary, but others, such as the various Linux distributions, are open source.