microsoft visual studio 2017 compiler version

We expect IntelliSense to be correct in the next preview of 15.7. We’re updating IntelliSense to correctly reflect the value of _cplusplus when compiling with MSVC. Also, the value of the _cplusplus macro is not affected by the /permissive- switch. Note that the MSVC compiler does not, and never will, support a C++11, C++03, or C++98 standards version switch. This chart shows the values of the _cplusplus macro with different switch combinations: /Zc:_cplusplus switch And the /std:c++latest switch, used to enable features from the Standard currently in development, sets a value that is more than the current Standard. If you compile in C++17 mode the macro will be set to “201703L”. If you’re compiling in C++14 mode the macro will be set to “201402L”. The version reported by the _cplusplus macro also depends upon the standard version switch used. We’ll continue to require use of the /Zc:_cplusplus switch for all minor versions of MSVC in the 19.xx family. We tried updating the macro by default and discovered that a lot of code doesn’t compile correctly when we change the value of _cplusplus. You need to compile with the /Zc:_cplusplus switch to see the updated value of the _cplusplus macro. It’s just that the new value is much more accurate than always reporting “199711L”.

The value of the _cplusplus macro doesn’t imply that we no longer have any conformance bugs. Now that our conformance catch-up work is drawing to a close we’re updating the _cplusplus macro to reflect the true state of our implementation. This macro has stubbornly remained at the value “199711L”, indicating (erroneously!) that the compiler conformed to the C++98 Standard. The MSVC compiler’s definition of the _cplusplus predefined macro leaps ahead 20 years in Visual Studio 2017 version 15.7 Preview 3.

Microsoft visual studio 2017 compiler version