RL> B) OS/2 style .exe files that require EMX.DLL to run.  
 RL> (These are the smallest, but they need a dll to run.)

 RL> C) Free-standing OS/2 style .exe files.  (No DLL 
 RL> required, they run on their own.  This is what all the 
 RL> OTHER OS/2 c++ compilers produce.)
 
This is not accurate information.  MSC, IBM Cset++ and Borland C++ for OS/2
all support this feature.  Watcom does not (something I didn't realize till
I saw someone mention it here just a short while ago). 

This feature is rarely used for stand-alone programs,  and probably
shouldn't be (same argument as for VROBJ.DLL that I started a few days
ago).

For large multi-process,  multi-dll projects,  sometimes having the CRT in
a dll is actually a prerequisite.  

I have a feeling that many EMX fans want to argue that it is better to have
everyone use exactly the same dll (emx.dll or whatever it is called), so
that it need not be shipped in every *.zip file.  This causes the
versioning problem I mentioned about VROBJ.DLL (in vx-rexx). 

IBM actually _insists_ that you create a new CRT.DLL with a unique name for
your product;  so that it will NOT be shared with anyone else.


--- Maximus/2 2.02p1