Mail Archives: djgpp/1997/09/11/07:04:36
In article <5v5fm1$iku$1 AT vixen DOT cso DOT uiuc DOT edu>, *bowlin*@*uiuc.edu* says...
>
>In article <34148F08 DOT 7A16 AT pacbell DOT net>, bndwgn AT pacbell DOT net says...
>>
>>
>>Avery Lee wrote:
>>Only the
>>> crappiest of 32-bit compilers (hmmm... Borland? :) ) would be beaten by a
>>> 16-bit compiler in terms of the speed of a serious program.
>>>
>>>
>>> -- Avery Lee (Psilon AT concentric DOT net)
>>
>>This comment is of some concern to me. I use Borland compilers, and am
>>about to upgrade to the new version (either Builder or 5.0 (right?)).
>>Is there some significant reason Borland is bad? Should I go with
>>something else? (Please dont say DJGPP, I'm addicted to the IDE).
>>
>>I'm not interested in getting drawn into a best compiler war, but if
>>there is a good reason to avoid the new Borland compilers, I would like
>>to know before I go spend several hundred dollars on one.
>
>1.)BC++ 5.02,Symantec C++ and Watcom C++ produce faster and smaller
>executables than MSVC++ 5.0.
>
>2.)BC++ 5.02 supports OWL and MFC 4.2.
>
>3.)BC++ 5.02 is compatible with C++ builder
>4.) the help system on MSVC++ 5.0 is SLOW even on a dual 300 MHz Pentium II
> with 128MB Ram.
>>Thanks.
>>
MSVC++ is not a tool for game programming. DJGPP/Watcom certainatly are.
- Raw text -