#DLL Memory Access
Under WIN16 (Windows 3.x) it's legal for two applications to dynamically link
to a common DLL and, effectively, share data through that DLL's data segment by
calling DLL API's that accessed that data.
Our question is … Is this capability legal under WIN32 or WIN32s ? Let's
assume, for example, that App 1 calls a DDL function that allocates some global
memory (for a FIFO). App 2 then calls another function in that same DLL that
loads data into that FIFO. Would this constitute a protection violation under
WIN32 or WIN32s ? It seems to us that, since the global memory allocated for
the FIFO "belongs" to App 1 it would be illegal for App 2 to use the same DLL
to write to that FIFO. Is this true ?
If this is a protection violation then is it true that DLLs can no longer be
used to share data between applications ? Is DDE, now, the only portable
method for data sharing between applications ?
There are 2 Replies.