3 ms·
But in 2017, there will be another significant new standard, C++17. I wonder if VS will not support it until 2022, if they remain 6 years behind on new language
by hellofunk 10y ago
But in 2017, there will be another significant new standard, C++17. I wonder if VS will not support it until 2022, if they remain 6 years behind on new language standards?
- pjmlp 10y agoPeople like to complain about VS, but they are quite good in what concerns commercial C++ compilers. http://en.cppreference.com/w/cpp/compiler_support http://en.cppreference.com/w/cpp/compiler_support And C++ compiler support page doesn't provide information about the likes of TI and similar embedded OEMs, otherwise that reddish colour would be even bigger.
- adrianN 10y agoIn the embedded world you can consider yourself lucky if you get a halfway working c++98 compliance.
- krona 10y agoI agree with your general point, but frankly the only feature of C++17 I'm interested in is await/resume and that's already supported in VS 2015.
- gpderetta 10y agoAwait/resume won't be in c++17, as it is very contentious. It will be first released as a Technical Report.
- ntauthority 10y agoVS2017 already is quite far into supporting C++14/C++17 features, except that expression SFINAE and extended constexpr were not viable to implement on the original (dated) compiler frontend and therefore the past years have been spent on rewriting large portions of the compiler. The VC team blog provides fairly decent information with regards to reasoning and progress behind this.
- Scea91 10y agoC++17 won't be that significant. All of the major features have been postponed to later revisions.