why is Visual Studio Community 2017 c++ standard is c++98?
Clash Royale CLAN TAG#URR8PPP
up vote
6
down vote
favorite
Yesterday I upgraded to the latest VS community 2017 (the previous one was installed last year) and wanted to check the c++ standard, so I run a code that checks it (picture attached) and as it turnes out, I have c++98 (!!), I don't understand why I don't have the latest c++ standard?
c++ visual-studio standards
 |Â
show 3 more comments
up vote
6
down vote
favorite
Yesterday I upgraded to the latest VS community 2017 (the previous one was installed last year) and wanted to check the c++ standard, so I run a code that checks it (picture attached) and as it turnes out, I have c++98 (!!), I don't understand why I don't have the latest c++ standard?
c++ visual-studio standards
Try changing the related project properties.
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
Possible duplicate: Is C++11 available in Visual Studio 2017?
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
I'm voting to close this question as off-topic because this should be asked the vendor. SO is not Microsoft support.
– too honest for this site
2 hours ago
@toohonestforthissite Ideally the fact that you had to type up a custom close reason when you found that none of the predefined close reasons applied would have been a hint to you to check what is and is not topical here. This question is perfectly acceptable. It is well-known that Visual Studio is not stuck in 1998, so asking what's wrong when a program suggests otherwise is fine. If Visual Studio were stuck in 1998, then I might agree that a question on why it is would be better asked elsewhere.
– hvd
2 hours ago
@hvd: Non sequitur! Why do you think custom close reasons exist?
– too honest for this site
2 hours ago
 |Â
show 3 more comments
up vote
6
down vote
favorite
up vote
6
down vote
favorite
Yesterday I upgraded to the latest VS community 2017 (the previous one was installed last year) and wanted to check the c++ standard, so I run a code that checks it (picture attached) and as it turnes out, I have c++98 (!!), I don't understand why I don't have the latest c++ standard?
c++ visual-studio standards
Yesterday I upgraded to the latest VS community 2017 (the previous one was installed last year) and wanted to check the c++ standard, so I run a code that checks it (picture attached) and as it turnes out, I have c++98 (!!), I don't understand why I don't have the latest c++ standard?
c++ visual-studio standards
c++ visual-studio standards
edited 2 hours ago
asked 2 hours ago
eagleye
51128
51128
Try changing the related project properties.
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
Possible duplicate: Is C++11 available in Visual Studio 2017?
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
I'm voting to close this question as off-topic because this should be asked the vendor. SO is not Microsoft support.
– too honest for this site
2 hours ago
@toohonestforthissite Ideally the fact that you had to type up a custom close reason when you found that none of the predefined close reasons applied would have been a hint to you to check what is and is not topical here. This question is perfectly acceptable. It is well-known that Visual Studio is not stuck in 1998, so asking what's wrong when a program suggests otherwise is fine. If Visual Studio were stuck in 1998, then I might agree that a question on why it is would be better asked elsewhere.
– hvd
2 hours ago
@hvd: Non sequitur! Why do you think custom close reasons exist?
– too honest for this site
2 hours ago
 |Â
show 3 more comments
Try changing the related project properties.
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
Possible duplicate: Is C++11 available in Visual Studio 2017?
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
I'm voting to close this question as off-topic because this should be asked the vendor. SO is not Microsoft support.
– too honest for this site
2 hours ago
@toohonestforthissite Ideally the fact that you had to type up a custom close reason when you found that none of the predefined close reasons applied would have been a hint to you to check what is and is not topical here. This question is perfectly acceptable. It is well-known that Visual Studio is not stuck in 1998, so asking what's wrong when a program suggests otherwise is fine. If Visual Studio were stuck in 1998, then I might agree that a question on why it is would be better asked elsewhere.
– hvd
2 hours ago
@hvd: Non sequitur! Why do you think custom close reasons exist?
– too honest for this site
2 hours ago
Try changing the related project properties.
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
Try changing the related project properties.
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
Possible duplicate: Is C++11 available in Visual Studio 2017?
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
Possible duplicate: Is C++11 available in Visual Studio 2017?
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
I'm voting to close this question as off-topic because this should be asked the vendor. SO is not Microsoft support.
– too honest for this site
2 hours ago
I'm voting to close this question as off-topic because this should be asked the vendor. SO is not Microsoft support.
– too honest for this site
2 hours ago
@toohonestforthissite Ideally the fact that you had to type up a custom close reason when you found that none of the predefined close reasons applied would have been a hint to you to check what is and is not topical here. This question is perfectly acceptable. It is well-known that Visual Studio is not stuck in 1998, so asking what's wrong when a program suggests otherwise is fine. If Visual Studio were stuck in 1998, then I might agree that a question on why it is would be better asked elsewhere.
– hvd
2 hours ago
@toohonestforthissite Ideally the fact that you had to type up a custom close reason when you found that none of the predefined close reasons applied would have been a hint to you to check what is and is not topical here. This question is perfectly acceptable. It is well-known that Visual Studio is not stuck in 1998, so asking what's wrong when a program suggests otherwise is fine. If Visual Studio were stuck in 1998, then I might agree that a question on why it is would be better asked elsewhere.
– hvd
2 hours ago
@hvd: Non sequitur! Why do you think custom close reasons exist?
– too honest for this site
2 hours ago
@hvd: Non sequitur! Why do you think custom close reasons exist?
– too honest for this site
2 hours ago
 |Â
show 3 more comments
1 Answer
1
active
oldest
votes
up vote
12
down vote
accepted
The value of __cplusplus
is temporarily intentionally non-conformant by default for current versions of Visual Studio in order to avoid breaking existing code. It does not mean your compiler does not support any C++11 (or newer) features.
Quoting from MSVC now correctly reports __cplusplus:
/Zc:__cplusplus
You need to compile with the
/Zc:__cplusplus
switch to see the updated value of the__cplusplus
macro. 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
. We’ll continue to require use of the/Zc:__cplusplus
switch for all minor versions of MSVC in the 19.xx family.
success! I followed the instructions on setting /Zc:__cplusplus to enabled and I see I have c++14 (201402). This is the guide for doing this: docs.microsoft.com/en-us/cpp/build/reference/…
– eagleye
1 hour ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
12
down vote
accepted
The value of __cplusplus
is temporarily intentionally non-conformant by default for current versions of Visual Studio in order to avoid breaking existing code. It does not mean your compiler does not support any C++11 (or newer) features.
Quoting from MSVC now correctly reports __cplusplus:
/Zc:__cplusplus
You need to compile with the
/Zc:__cplusplus
switch to see the updated value of the__cplusplus
macro. 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
. We’ll continue to require use of the/Zc:__cplusplus
switch for all minor versions of MSVC in the 19.xx family.
success! I followed the instructions on setting /Zc:__cplusplus to enabled and I see I have c++14 (201402). This is the guide for doing this: docs.microsoft.com/en-us/cpp/build/reference/…
– eagleye
1 hour ago
add a comment |Â
up vote
12
down vote
accepted
The value of __cplusplus
is temporarily intentionally non-conformant by default for current versions of Visual Studio in order to avoid breaking existing code. It does not mean your compiler does not support any C++11 (or newer) features.
Quoting from MSVC now correctly reports __cplusplus:
/Zc:__cplusplus
You need to compile with the
/Zc:__cplusplus
switch to see the updated value of the__cplusplus
macro. 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
. We’ll continue to require use of the/Zc:__cplusplus
switch for all minor versions of MSVC in the 19.xx family.
success! I followed the instructions on setting /Zc:__cplusplus to enabled and I see I have c++14 (201402). This is the guide for doing this: docs.microsoft.com/en-us/cpp/build/reference/…
– eagleye
1 hour ago
add a comment |Â
up vote
12
down vote
accepted
up vote
12
down vote
accepted
The value of __cplusplus
is temporarily intentionally non-conformant by default for current versions of Visual Studio in order to avoid breaking existing code. It does not mean your compiler does not support any C++11 (or newer) features.
Quoting from MSVC now correctly reports __cplusplus:
/Zc:__cplusplus
You need to compile with the
/Zc:__cplusplus
switch to see the updated value of the__cplusplus
macro. 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
. We’ll continue to require use of the/Zc:__cplusplus
switch for all minor versions of MSVC in the 19.xx family.
The value of __cplusplus
is temporarily intentionally non-conformant by default for current versions of Visual Studio in order to avoid breaking existing code. It does not mean your compiler does not support any C++11 (or newer) features.
Quoting from MSVC now correctly reports __cplusplus:
/Zc:__cplusplus
You need to compile with the
/Zc:__cplusplus
switch to see the updated value of the__cplusplus
macro. 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
. We’ll continue to require use of the/Zc:__cplusplus
switch for all minor versions of MSVC in the 19.xx family.
answered 2 hours ago


hvd
113k11193272
113k11193272
success! I followed the instructions on setting /Zc:__cplusplus to enabled and I see I have c++14 (201402). This is the guide for doing this: docs.microsoft.com/en-us/cpp/build/reference/…
– eagleye
1 hour ago
add a comment |Â
success! I followed the instructions on setting /Zc:__cplusplus to enabled and I see I have c++14 (201402). This is the guide for doing this: docs.microsoft.com/en-us/cpp/build/reference/…
– eagleye
1 hour ago
success! I followed the instructions on setting /Zc:__cplusplus to enabled and I see I have c++14 (201402). This is the guide for doing this: docs.microsoft.com/en-us/cpp/build/reference/…
– eagleye
1 hour ago
success! I followed the instructions on setting /Zc:__cplusplus to enabled and I see I have c++14 (201402). This is the guide for doing this: docs.microsoft.com/en-us/cpp/build/reference/…
– eagleye
1 hour ago
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52465524%2fwhy-is-visual-studio-community-2017-c-standard-is-c98%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Try changing the related project properties.
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
Possible duplicate: Is C++11 available in Visual Studio 2017?
– Ã€Î¬Î½Ã„α ῥεῖ
2 hours ago
I'm voting to close this question as off-topic because this should be asked the vendor. SO is not Microsoft support.
– too honest for this site
2 hours ago
@toohonestforthissite Ideally the fact that you had to type up a custom close reason when you found that none of the predefined close reasons applied would have been a hint to you to check what is and is not topical here. This question is perfectly acceptable. It is well-known that Visual Studio is not stuck in 1998, so asking what's wrong when a program suggests otherwise is fine. If Visual Studio were stuck in 1998, then I might agree that a question on why it is would be better asked elsewhere.
– hvd
2 hours ago
@hvd: Non sequitur! Why do you think custom close reasons exist?
– too honest for this site
2 hours ago