CH> (I know, I know, freeing memory in a different program 
 CH> source file than it was allocated is generally 
 CH> considered a design flaw, but I couldn't think of any other way to do it.)

How I handled a similar case under Windows:

The DLL would only hand back a 'handle' to the original structure, but
would never be given access to its internals except through API calls.  I
would then use a 'lookup table' in the DLL to find the actual structure (so
I could have multiple programs querying the DLL at once).  However, I
'cheated': I used DECLARE_HANDLE32(MyDLLHandleType) to create the type and
actually gave back the pointer I was using.  ;-)  No actual tables, but the
user of the DLL didn't know that.

A requirement was that the user would have to 'close' the handle (and all I
did was cast the pointer back to the real type and delete it...).

This worked with both static and dynamically linked DLLs.


--- Maximus/2 3.01