-=> Quoting Stephane Bessette to Tom Almy <=-

 -=> Quoting Tom Almy to Matthew Laird <=-

 -=> Quoting Matthew Laird to All <=-

 TA> Last summer I basically "gave up" trying to develop Windows
 TA> applications under OS/2 and installed a Windows NT partition. If you
 TA> can find a copy of 3.51, it will co-exist in an HPFS environment and
 TA> allow Visual C++, any version, as well as other 32 bit compilers to
 TA> work with full functionality.

 SB> What about using Watcom C/C++?  I would think that you could
 SB> use the compiler in OS/2 mode (i.e. the OS/2 IDE) to generate a
 SB> Windows executable, and then start that executable as a regular WinOS2
 SB> application.

If it were for my own personal use, that's the way I'd go. However I do
consulting and contract programming, so I have to use the compilers my clients
use. Microsoft C++ and the latest Borland versions don't run under OS/2, and
this is what they are using for development.

The only OS/2 positive part of all of this is that once compiled everything
will run under Win-OS/2. At least up till now I've avoided writing anything
that has required features beyond Win32s 1.25.

Tom


--- Blue Wave/DOS v2.30