in a message to All, Gary Chambers claims to have written:

 GC> Why, apparently, are the resultant .EXE files created by
 GC> Borland C++ for OS/2 1.5 so much larger than their CSet/2
 GC> counterparts?  For example, the disk that accompanies Real
 GC> World Programming for OS/2 2.11 contains examples compiled
 GC> with CSet/2.  When I compile the same exact source code with
 GC> my Borland compiler, the EXE skyrockets in size.  Is there
 GC> something (aside from linking the DLL version of the RTL) I
 GC> can do to decrease this size?  Thanks...

Just a guess, but are you including debug info in the .EXE created by BCOS2
but not the one created by CSet/2?. Also, is the Borland compiler optimized
for speed or size?. If for speed then parts of the code are being
replicated in the executable in order to reduce function calls (each of
which introduces an additional time delay), so your program runs faster at
the expense of compactness.

Groetjes,
             Brad 
---