| From: | Jan-Erik Karlsson |
| Date: | 14 Aug 2001 at 19:39:29 |
| Subject: | [amiga-c] Re: GCC and exceptions... |
Hello, Jesper
On 14-Aug-01, you wrote:
JS >> Hello, Jesper
JS >>
JS >> On 14-Aug-01, you wrote:
JS >>
JS >>>> Btw: does anyone know any good MS-VC++ programming
JS >> mailinglists (like
JS >>>> this
JS >>>> one)? Preferably one where people aren't afraid to admit that
JS >> they
JS >>>> are
JS >>>> wasting their time with the stupid Win 32 API... ;-)
JS >>>
JS >>> I have to admit that I use MSVC++ every day at work, and I've
JS >> done
JS >>> quite a lot with the Win32-API (the API in itself isn't that bad
JS >>> really, and usually you just hide it behind some class :)... But
JS >> that
JS >>> would bring us off-topic in this group, wouldn't it? :)
JS >>
JS >> is anybody actually using MSVC to compile C++ code now? MSVC is
JS >> not regarded as a good C++ compiler (actually StormC V3 is probably
JS >> just as good).
JS >
JS > Everyone I know that does Wintel-development uses MSVC. MSVC is a VERY
JS > good C++ compiler (fast, optimizing really good, etc), and has a
JS > still-to-be-beaten IDE (the debugger just RULES! StormC comes close
JS > there, but with Edit-And-Continue, it moves to a different level). It
JS > reduces the development-time quite a bit, and with a few aids (Visual
JS > Assist, BoundChecker, etc) you can even cut it some more.
here is some true facts of how 'good' MSVC is
Borland BCC 5.5 (free) 63%
Comeau C++ 4.2.44 98%
GCC 2.95.2 98%
HP aC++ A.03.26 98%
IBM VisualAge 5.0 99%
Intel C/C++ 4.5 96%
KAI C++ 4.0b 98%
CodeWarrior 90%
MSVC++ 77%
Sun Visual Workshop 95%
these figures are on how close the compilers are to the C++ standard and how
they are capable to
accomodate the C++ standard (which means that Borland and Microsoft will NOT
be able to comply to the C++ standard how much they try to pretend to do
it), and yes this 'official' figures.
MSVC does NOT comply to the standard with regard to such crucial elemnts as
how destructor's are handled.
MSVC does NOT free memory in the correct way or in the correct order in
destructor handling.
MSVC does NOT comply to the standard with regard to nested classes and
templates.
MSVC does NOT comply to the standard with regard to STL it uses the old HP
STL which is NOT compatible with the current standard.
MSVC does NOT support partial template specialization and will NOT ever.
With kind regards,
Jan-Erik Karlsson
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/