Visualstudio2013preview's support for c++11
The 3-Day Microsoft Build 2013 conference ended, as Microsoft's annual developer conference, Microsoft also did a lot of work: many products (including Windows 8.1 and Visual Studio Preview) released, Channel9 full stream, You can view all the contents of the meeting on the http://channel9.msdn.com/Events/Build/2013 side.
Although the entire build conference is not as lively as Google's I/O and Apple's WWDC (Google and Apple fans are more), I have been looking forward to it, and the biggest expectation is that herb Sutter has pledged to provide a better support for c++11 vs version in the first half of 2013. Herb Sutter (chief architect of Visual C + +, chairman of the C + + Standards Committee, can be said to be one of the most influential people in the C + + field) on the third day of the Build conference, a speech titled "The Future of C + +", describes the Visual Studio Preview's support for c++11. Before this speech, I had installed Visual Studio preview and tried some of the c++11 features that were not supported in Visual Studio 2012, and almost came up with a support list.
OK, or take a look at the official Roadamp given by Herb Sutter:
This is my speech from the Herb Sutter of the PPT, note the title: According to Sutter's introduction, Visual Studio did not set the target directly as c++11, but positioning as c++14 wave, the so-called c++14 wave, is with c++14 (c + + A minor release after 11, as a supplement to C++11, was formed earlier this year, and its draft has been approved by the C + + standards Committee, including a number of new libraries.
VC + + 2012 more than VC + + c++11 characteristics in the first column, including the delegate constructor , Unified Initialization list and variable template parameters and so on, of course, there are some C + + 14 Features (Cbegin and Make_unique, etc.).
VC + + Preview is not supported, but this year the VC + + RTM version, will be added non-static data member initialization, =default,=delete and using aliases Support, that is to say, vc++2013 RTM basically supports the common features of c++11, but does not include constexpr (Sutter said that temporarily does not support constexpr because VC no ast tree, is now adding AST, I feel very strange, before vc+ + How is the compilation process completed? ) and noexcept.
The rest of the c++11 feature is in a development version called Post-rtm OOB CTP, and some features are being planned, and it seems that the idea of Herb Sutter is actually aimed directly at C++14, based on the current frequency of VS's release, All of these features I feel like around 2015 almost all have.
Say what you think, in the support of c++11, Visual C + + for GCC and clang, of course, is a big lag, two open source compilers are already feature complete. But VC + + as a commercial product, of course, have their own consideration. Microsoft has its own expansion of C + + (C + +/CLI, C++/CX, C + + AMP), and C + + for Microsoft's status is not as high as C #, the entire VC + + team is relatively small (you can go to http://channel9.msdn.com/Events/ build/2013/2-306 here to see the comments below), in this case, I personally feel that it is not easy to do so. I personally admire Herb Sutter, a person and so many important positions, all aspects of things are handled very well, in addition to their own often write technical blog, very curious how he used the time!
In the process of watching the whole video, there is a deep feeling: there seems to be no too many developers interested in the technology, the atmosphere is not strong enough, unlike some special C + + conference has such a good atmosphere, such as going native,c++ and beyond and meeting C + + and so on. Right, Herb Sutter in the PPT finally said, this year's going native will be in September 4-6, very much looking forward to this pure C + + conference!
This article by the Bean John Blog backup expert remote One click release
Visualstudio2013preview Support for C++11 (reprint)