I'm not defending or supporting Microsoft VC++, but just want to add
some perspective.
>>First, MFC is the ugliest framework I ever seen
Yes, and it's also been accused of not being object oriented. Way back,
when C++ was new, Microsoft modeled MFC on its SDK API names so
that it would be familiar to the existing base of Windows/C programmers.
>>Second, Microsoft's C++ compiler is a disaster. It doesn't even
>>know how to handle simple things like:
>> for (int i=1; i<10; i++) { // do some stuff... }
>> for (int i=1; i<10; i++) { // do some other stuff... }
Yes, the new C++ standard says "i" should go out of scope leaving the
"for loop", whereas the old C++ standard says "i" should stay in scope
until the end of the function. The new standard meant existing code
would break, so Microsoft opted to preserve backward compatibility.
Microsoft does have a compiler switch to support the new standard, but
some (including me) argue Microsoft has that switch reversed. The
switch should support Microsoft extensions; the compiler by default
should support standard C++.
>>we have a cross platform code base
>>compiled for several environments, and VC++ is the
>>one which gives us the most headaches and troubles.
I agree. Microsoft and cross platform goals are at cross purposes.
Michael Yam
Y Technology, Inc.
[EMAIL PROTECTED]
