Hallo Jonathan,

Jonathan de Boyne Pollard schreef dit aan Jorgen De Gier:


 ZZ>>
 >> JDG> Wait a minute, can you run VC++ 1.5 within Win-OS/2?
 >>
 >> I'd ask Jon, I believe it was he who figured out a previous MS-OS/2
 >> riddle.
 ZZ>>

 JdBP>   BTW, from experience with Microsoft Visual C++ 2.x as a C++ language
 JdBP>   implementation, I wouldn't recommend it to anyone.  Even the latest
 JdBP>   editions have fundamental language problems, such as mistakenly
 JdBP>   thinking that you are doing function overloading, even when all that
 JdBP>   you've done is spelled a parameter name differently in two
 JdBP>   declarations.

VC++ isn't my choise. I use BC++4.5 at home, but at work they use VC++.
I used to like VC++ because of it's point'n'click code generation until someone
told me BC++ did have the same thing called ClassExpert! Men, I hate online docs!

 JdBP>   If you want a decent *DOS+Windows* compiler, then Watcom C++ or
 JdBP>   MetaWare High C++ for DOS are recommended alternatives.  Both of them
 JdBP>   implement the C++ language fairly robustly to ARM level (and beyond in
 JdBP>   MetaWare's case) and can compile DOS and DOS+Windows applications.

 JdBP>   The MetaWare High C++ for DOS compiler runs straight out of the box in
 JdBP>   an OS/2 2.10 and later Virtual DOS Machine without any trouble.

I ordered Visual Age C++ WITH all the docs. The primary reason is IBM and it
has a class library. I'm used to these. Maybe I'm to lazy to use the 'API'
way. I'm programming Windows using OWL since BC++3.1 was released. It's
very easy, but it makes me very lazy. I almost bought Watcom until I read
in your (excelent) pros&con list that it doesn't supply a (OS/2)
class-lib.
Same thing about High C++, besides it's huge price.

 JdBP>   The Watcom C++ compiler is OS/2 hosted, so you won't have any of the
 JdBP>   headaches over DOS extenders and their limited memory that you have
 JdBP>   with Borland C++ or Microsoft Visual C++ (Have you ever had Borland
 JdBP>   C++ fall over with an exception 13 simply because its DOS extender
 JdBP>   couldn't allocate enough DPMI memory, but rather than report that it
 JdBP>   just up and dies ?  I have.).  And you can compile native OS/2
 JdBP>   programs as an added bonus (as it were) ...

I never had any problem running BC++ running in Win-OS2. Enable DMPI, DMPI mem
set to 32MB, XMS to 16MB. As you wrote to someone else, OS/2 is almost the
perfect platform for developing Win-apps.

 >> JdeBP <
 >> Run, do not walk, to your nearest FIDONET files site for FGA-OS2D.ZIP, <
 >> the Frequently Given Answers from the OS2DOS echo.  If there is no     <
 >> Fernwood filebone site near you, you can also FREQ it from 2:440/4.0 . <

I will.

Ps. I dumped Borland for OS/2 PM. The OWL port stinks and the compiler is
unstable. I can't judged about the code-generation because I've hardly
programmed PM with it.
I'm just keep using it for simple text-mode programs because it compiles
extreemly fast.
Borland surprised me by giving me a free update (BC++4.51). They just
mailed it to me. I didn't even ask for it!


Toedeloe,
Jorgen de Gier

--- GEcho 1.00