>>>From the community we also often hear that Concepts is another widely anticipated feature, but this too will miss the cut for VS2010.
Didn't you guys read this or check the MSDN blogs?
Get Microsoft Visual C++ Express here or CodeBlocks here.
Get STLFilt here to radically improve error messages when using the STL.
Get these two can't live without C++ libraries, BOOST here and Loki here.
Check your code with the Comeau Compiler and FlexeLint for standards compliance and some subtle errors.
Always use [code] code tags [/code] to make code legible and preserve indentation.
Do not ask for help writing destructive software such as viruses, gamehacks, keyloggers and the suchlike.
Although we have covered this before (many thanks Marc G and Russco for providing both the links and excerpts above) I did want to reiterate that the reasons why a only a subset of the C++0x Standard will make VC10 are along the lines of: 1) C++0x and VC10 planning/development overlap, 2) stability of some aspects of the C++0x Standard during this time and 3) trying to provide a coherent set of features. We see great value in many of the C++0x features that we will just not have time to do in VC10, so please see our early adoption of some features as strong support for C++0x. For completeness, form the original post:
Now during the VS2010 planning stage, C++0x was still in a state of flux and this presented an issue to us. Of course we wanted to be highly conformant to the new standard and many of the new C++0x features looked like very valuable additions for our customers. However, without the standard being finalized, potentially until after we ship, and with finite time and resources on our team, we need to target a coherent subset of C++0x features that were relatively stable for inclusion in VS2010 (seems Standards Work seems to take even longer then Product work, believe it or not). So where did we end up let us look at some of the features that are already available in the aforementioned CTP: