3 ms·
>The problem is really simply that Microsoft was never interested, at least until very recently, to have a truly standards compliant compiler. I think Microsof
by Kristine1975 11y ago
>The problem is really simply that Microsoft was never interested, at least until very recently, to have a truly standards compliant compiler.
I think Microsoft neglected C++ over .Net before suddenly changing their minds and deciding to support C++ more.
VS2010 was one of the first compilers (even before gcc/clang) to support parts of the preliminary C++0x standard (e.g. lambda functions). But when the final standard was released they fell behind in implementing it.
- bstamour 11y ago> VS2010 was one of the first compilers (even before gcc/clang) GCC supported C++0x features back when they thought the standard would be released before 2010. Hence the 0x, not 1x. I remember using the `-std=c++0x` flag back in 2008, when I first took a course on C++, which is a few years before VS2010.