Re: REMINDER: Don't dynamically link distributed executables (was Re: question about paragraph in INSTALL file)
Rick Campbell writes:
As far as I can tell, while Sun is fighting Microsoft in the public
arena, their technical decisions are some of the biggest reasons
around for switching to the dark side, er, NT. I'm not sure that even
HPs C++ compiler is as bad as Sun's is these days. It's really kind
of embarrassing to have to have a zillion backward compatibility hacks
so that code that works with all of the ANSI compatibility that comes
with Visual C++ can still deal with something as archaic as
Sparcworks(*).
I'm not excatly sure *what* you're saying here - are you
referring to ANSI C, or ANSI C++ (or ANSI Common Lisp? Nah...)
For what it's worth, the compiler in Visual C++ has a number
of severe bugs/shortcomings. For instance, at warning level 3 (the
highest level recommended for normal use) the compiler does not catch
the following typo:
foo::iterator it;
for (it = mycollection.begin; ...) // should be mycollection.begin()
The libraries, likewise (Visual C++ 5.0 shipped with a
severely broken STL). The integrated environment is even worse; they
even *default* to saying that the Tab spacing is 4 characters!
Meanwhile all their C++ effort seems to be in building
a friggin graphical development environment. Like, someone should
tell them that you're supposed to get the core functionality in place
before you starting playing with the bells and whistles. Jeez.
Seems to work for Microsoft :-)
//Raymond.