-=> Quoting Jonathan de Boyne Pollard to Tom Almy <=-

 TA>
 > Microsoft C++ and the latest Borland versions don't run under OS/2, [...]
 TA>

 JdBP> The Borland C++ for DOS compilers _do_ run under OS/2 Warp, and have
 JdBP> done for years.  As of OS/2 Warp 4, IBM and Borland appear to have come
 JdBP> to an agreement as to the DPMI spec, and Borland's command-line tools
 JdBP> now work without fiddling the DPMI settings.

Some of their command line tools (their 32 bit DOS compiler for example, which
came with their "Powerpack for DOS") wouldn't work with any DPMI
setting under
Warp 3. I found it inferior to DJDelorie's free GCC port, so I don't need to
use it.

I like using GCC, BTW. By using the OS/2 EMX port it's very easy to write
computation programs that run under OS/2 or DOS interchangably. (I stress
computation because the common user interface between the two isn't very
large.)


 JdBP> As for "latest Borland version", read the small print carefully.
 JdBP> Borland are doing the Microsoft version number scam.  On the side of
 JdBP> the box of Borland C++ 5.0 for DOS, it states that the actual
 JdBP> _compiler_ is Borland C++ 4.52.

Basically 4.52 was the last version to run under DOS. 5.00 requires WIN32.
Borland is nice enough to ship 4.52 in the box with 5.00. Note that either one
will target any Microsoft OS. (Microsoft also supplies 16 bit version 1.5 in
VC++ 4.x, however 1.5 only targets 16 bit OSes and 4.x only targets 32 bit
OSes).

I made an interesting discovery -- they provide library sources on the CD
which *include* conditional compilation for OS/2! I haven't tried it out yet,
but it looks like I could utilize such nice things as their conio.h functions
under OS/2.


Tom


--- Blue Wave/DOS v2.30