CH> I have a program here that attempts to use a DLL for a 
 CH> portion of it's functions.  The problem is that when I 
 CH> realloc or free a pointer allocated by the DLL in the 
 CH> program's EXE, the thing crashes.

Then don't do that .

You are correct in your thinking that there are two runtimes here; one in
the DLL and one in the EXE.

The quickest solution is to use the version of the runtime that is itself a
dll (so that your EXE and DLLs all use the same runtime) -- but I don't
think Watcom supports this feature.

A better solution would be to change your design -- I don't think it is a
good design to allocate memory in one place (a "place" being the
OOP "class" idea) and free it somewhere else -- same goes for
opening/closing files, etc.

If you have already made the decision that some code is so isolated that it
belongs in a DLL,  I find it odd that such an intimate relationship exists
between your EXE and DLL.

I usually write a DLL interface (ie: the APIs it exports) as if it will be
called from a different language (or C compiler,  where you _definitely_
can't let the runtimes mix).



--- Maximus/2 3.00