On Friday March 08 1996 at 02:25, Peter Fitzsimmons wrote to Coridon Henshaw:

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

It doesn't appear to, but you never can tell, considering the bad
documentation that they ship...

 PF> A better solution would be to change your design -- I don't think it is a
 PF> good design to allocate memory in one place (a "place"
being the OOP
 PF> "class" idea) and free it somewhere else

What I have is a recursive directory sweep function that allocates memory
to hold each filename.  This code must deal with HPFS filenames, so it
isn't possible to reserve ~260 bytes in the file information structures for
each filename.

 PF> If you have already made the decision that some code is so isolated that it
 PF> belongs in a DLL,

The code is not isolated - it's used by several EXEs in the same package.

If I statically link the DLL code to each EXE, the entire package swells
from ~100KB to ~200KB.

--- GoldED/2 2.50 UNREG