Mail Archives: djgpp/1997/09/08/20:20:01
In group rec.games.programmer, Adam W Lee says...
> : Possibly true with respect to the ancient 16-bit MSVC++ 1.0 that the
> : original poster mentioned and your 486 system. But if we consider more
> : recent 32-bit versions, 4.2 and 5.0, targetting Pentium systems, then gcc
> : falls way behind. It also trails Watcom and Borland with Intel's backend
> : optimizer.
>
> PGCC isn't too bad, though.
>
> : For DOS targets professionals used to choose Watcom, for Win32 targets they
> : usually choose Visual C++.
>
> I know a lot of people doing Win32 stuff in Watcom, though since you can
> so easily compile for both.
>
> : gcc is a little flaky with C++, exception handling is the most notorious
> : example. Also AT&T assembly syntax is a problem, not an advantage.
>
> OK, I'll give you that GCC's C++ isn't picture-perfect, but that's doding
> the fact that it supports 5 times as many languages as MSVC.
That's not much of an argument : you guys are talking about a C++
compiler! _So_ _what_ if the back end is used for other
languages?
BTW, VC++'s back end is used for Fortran, Visual Basic 5.0, and
an upcomming Java compiler. Visual C++ is also available to
produce Motorola and PowerPC code, MIPS, all Windows CE platforms
(which use none of these processors). It runs nativly on Dec
Alpha, also.
- Raw text -