Just a few thoughts on the List:

 JdBP>     +---------------+ Borland C++ 2.0 for Intel OS/2 +---------------+
 JdBP>     |                                                                |X


 JdBP> Very cheap.  Will run on

Is Borland,  in fact,  cheaper than IBM/Watcom in the EU?   It certainly
isn't over here; it upsets me everytime someone considers price a Borland
advantage.

 JdBP>    Full syntax colouring in the editor, and the debugger uses colour.
 JdBP>    Good standalone PM debugger (Turbo Debugger GX), and standalone
 JdBP>    text-mode debugger (which can both debug PM and 
 JdBP> text mode apps).  Comes
 JdBP>    with Borland's own very good PM Resource 
 JdBP> Workshop, including tools to

You use the word "good" when introducing these tools
(debugger,workshop), yet I believe even you have admitted they are buggy. 
You might consider dropping the "good" or changing it to
"good looking" instead :-).


re High C++:

 JdBP>    Supports
 JdBP>    customisable function calling conventions.

Watcom supports this as well.

 JdBP>    CON : Terrible text-mode debugger.

Can you use another product's debugger?

I think it might be nice to add any cross-compiler tricks you find.  For
example,  you can use Link386/IPMD on Watcom exe's if you work at it. Using
link386 on Watcom stuff almost always results in smaller programs (I should
note I've not tried this yet under v10).

There is a "demo" version of the Intel High C++ compiler on
devcon 6;  do you know how it is different from the real version?

I tried using it but ran into trouble early on;  I never actually got to
the point where I could compile a program with it.


--- Maximus/2 2.02p1