I see no reason why C ++ 0x should not be accepted. The C ++ community is much more promising than C. C has always been intended for the "portable assembler language", so the people who use it are actually not very interested in new attractive features. C ++ covers much wider, and I have not heard of a C ++ programmer who did not expect 0x. (It’s also my impression that the C ++ community is much more “strict” and really doesn’t want to move beyond the standard into undefined behavior, which implies that you are choosing C ++ 03 or C ++ 0X rather than a half-computed hybrid C programmers are generally much more relaxed in this regard and seem to enjoy using C89 with only a few C99 functions and headers)
However, Microsoft will be busy at least a few years earlier. Visual Studio 2010 will support a small part of C ++ 0x functions (lambdas, decltype and several others), but the vast majority will not be supported. We will have to wait for VS2012 or something else that ends in the next version in order to have some full support.
With GCC / g ++, the situation is much better, since most of the standard is already implemented (the standard committee does not like to use functions that have not been implemented and tested in the real compiler, and the GCC plug is often used for this)
But it will probably take some time to get stable and ready for production.
About C ++ "decline in popularity", I really do not see this. I do not think that C ++ has declined significantly in popularity in recent years. RAD developers, of course, have already jumped on the .NET, Python, or other languages or platforms. But where C ++ is used today, there are not many viable alternatives, and there is no reason why it should decline in popularity.
jalf
source share