GCC begins move to C++

GCC begins move to C++
[Development] Posted May 31, 2010 13:53 UTC (Mon) by corbet

It's now official: the GCC compiler is moving to a C++ implementation. "I am pleased to report that the GCC Steering Committee and the FSF have approved the use of C++ in GCC itself. Of course, there's no reason for us to use C++ features just because we can. The goal is a better compiler for users, not a C++ code base for its own sake." The next step is the bashing out of a set of C++ coding standards limiting the set of C++ language features which can be used.

Full Story (comments: none)

Since that aspect is just a codification of libraries already widely in use, no, it doesn't.
how about apple's closures proposal (http://www.open-std.org/JTC1/SC22/wg14/www/docs/n1451.pdf)? don't know if that'll make it into the standard, but that'd be a pretty big change for the better.

Meanwhile, it doesn't fix the one thing that's seriously wrong in C: the order of precedence of the bitwise operators.
In converting from B to C, one wants to replace & by && in such a statement; to make the conversion less painful, we decided to keep the precedence of the & operator the same relative to ==, and merely split the precedence of && slightly from &. Today, it seems that it would have been preferable to move the relative precedences of & and ==, and thereby simplify a common C idiom: to test a masked value against another value, one must write
if ((a&mask) == b) ...
where the inner parentheses are required but easily forgotten.
http://cm.bell-labs.com/cm/cs/who/dmr/chist.html