CM>
  > 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
  >
  >   Axe the debug information...
CM>

  Even without debug information, Borland C++ is not as good at
  generating small executables as some other compilers.

  Taking this program

    #include 

    int
    main ( int, char ** )
    {
            cout << "Hello there" << endl ;
            return 0 ;
    }

  and compiling it using both Borland C++ and Metaware High C++

  'bcc hello.cpp'

        10-12-94  16:33          44,557           0  bcc-hello.exe

  'hc hello.cpp'

        10-12-94  16:34          19,296          49  hc-hello.exe

  'bcc hello.cpp C2I.LIB'

        10-12-94  16:34           6,157           0  bcc-hello-dll.exe

  'hc -Hdlllib hello.cpp'

        10-12-94  16:35             832          49  hc-hello-dll.exe

  I've also compiled with optimisation switched on in both compilers,
  and disabling RTTI and exception handling in Borland C++.  Neither
  make any difference to the above figures.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 2.02