Enforcing C++98/03 for clang
up vote
2
down vote
favorite
The following code is rejected by latest gcc with -std=c++98 option enabled:
#include <random>
int main() {}
due to the c++11 nature of <random> header. But clang accepts it with no warning/error.
Is there a way to say clang to use the c++98/03 standard only? Maybe a bug?
c++ clang c++98
asked Nov 21 at 13:06
älёxölüt
1,86511446
|
show 1 more comment
up vote
2
down vote
favorite
The following code is rejected by latest gcc with -std=c++98 option enabled:
#include <random>
int main() {}
due to the c++11 nature of <random> header. But clang accepts it with no warning/error.
Is there a way to say clang to use the c++98/03 standard only? Maybe a bug?
c++ clang c++98
asked Nov 21 at 13:06
älёxölüt
1,86511446
1
Unfortunately most compilers seem to allow non standard elements by default (no idea why). OnGCCto force standard compliance you need the-pedantic-errorsflag. Maybe its the same forclang++?
– Galik
Nov 21 at 13:13
2
"Maybe a bug?" - Definitely a bug. One that's unlikely to be caught since legacy code won't actually include modern headers
– StoryTeller
Nov 21 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– älёxölüt
Nov 21 at 13:53
@StoryTeller: What exactly makes it a bug? If<random>is surrounded by one huge#if __cplusplus > 199711L, making it effectively empty in C++98, I'd be hard-pressed to find wording in C++98 making that a bug.
– MSalters
Nov 21 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 at 14:09
|
show 1 more comment
up vote
2
down vote
favorite
up vote
2
down vote
favorite
The following code is rejected by latest gcc with -std=c++98 option enabled:
#include <random>
int main() {}
due to the c++11 nature of <random> header. But clang accepts it with no warning/error.
Is there a way to say clang to use the c++98/03 standard only? Maybe a bug?
c++ clang c++98
asked Nov 21 at 13:06
älёxölüt
1,86511446
The following code is rejected by latest gcc with -std=c++98 option enabled:
#include <random>
int main() {}
due to the c++11 nature of <random> header. But clang accepts it with no warning/error.
Is there a way to say clang to use the c++98/03 standard only? Maybe a bug?
c++ clang c++98
c++ clang c++98
asked Nov 21 at 13:06
älёxölüt
1,86511446
asked Nov 21 at 13:06
älёxölüt
1,86511446
edited Nov 21 at 13:07
asked Nov 21 at 13:06
älёxölüt
1,86511446
asked Nov 21 at 13:06
älёxölüt
1,86511446
asked Nov 21 at 13:06
älёxölüt
1,86511446
1,86511446
1
Unfortunately most compilers seem to allow non standard elements by default (no idea why). OnGCCto force standard compliance you need the-pedantic-errorsflag. Maybe its the same forclang++?
– Galik
Nov 21 at 13:13
2
"Maybe a bug?" - Definitely a bug. One that's unlikely to be caught since legacy code won't actually include modern headers
– StoryTeller
Nov 21 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– älёxölüt
Nov 21 at 13:53
@StoryTeller: What exactly makes it a bug? If<random>is surrounded by one huge#if __cplusplus > 199711L, making it effectively empty in C++98, I'd be hard-pressed to find wording in C++98 making that a bug.
– MSalters
Nov 21 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 at 14:09
|
show 1 more comment
1
Unfortunately most compilers seem to allow non standard elements by default (no idea why). OnGCCto force standard compliance you need the-pedantic-errorsflag. Maybe its the same forclang++?
– Galik
Nov 21 at 13:13
2
"Maybe a bug?" - Definitely a bug. One that's unlikely to be caught since legacy code won't actually include modern headers
– StoryTeller
Nov 21 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– älёxölüt
Nov 21 at 13:53
@StoryTeller: What exactly makes it a bug? If<random>is surrounded by one huge#if __cplusplus > 199711L, making it effectively empty in C++98, I'd be hard-pressed to find wording in C++98 making that a bug.
– MSalters
Nov 21 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 at 14:09
1
1
Unfortunately most compilers seem to allow non standard elements by default (no idea why). On
GCC to force standard compliance you need the -pedantic-errors flag. Maybe its the same for clang++?– Galik
Nov 21 at 13:13
Unfortunately most compilers seem to allow non standard elements by default (no idea why). On
GCC to force standard compliance you need the -pedantic-errors flag. Maybe its the same for clang++?– Galik
Nov 21 at 13:13
2
2
"Maybe a bug?" - Definitely a bug. One that's unlikely to be caught since legacy code won't actually include modern headers
– StoryTeller
Nov 21 at 13:20
"Maybe a bug?" - Definitely a bug. One that's unlikely to be caught since legacy code won't actually include modern headers
– StoryTeller
Nov 21 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– älёxölüt
Nov 21 at 13:53
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– älёxölüt
Nov 21 at 13:53
@StoryTeller: What exactly makes it a bug? If
<random> is surrounded by one huge #if __cplusplus > 199711L, making it effectively empty in C++98, I'd be hard-pressed to find wording in C++98 making that a bug.– MSalters
Nov 21 at 14:06
@StoryTeller: What exactly makes it a bug? If
<random> is surrounded by one huge #if __cplusplus > 199711L, making it effectively empty in C++98, I'd be hard-pressed to find wording in C++98 making that a bug.– MSalters
Nov 21 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 at 14:09
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 at 14:09
|
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412721%2fenforcing-c98-03-for-clang%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Unfortunately most compilers seem to allow non standard elements by default (no idea why). On
GCCto force standard compliance you need the-pedantic-errorsflag. Maybe its the same forclang++?– Galik
Nov 21 at 13:13
2
"Maybe a bug?" - Definitely a bug. One that's unlikely to be caught since legacy code won't actually include modern headers
– StoryTeller
Nov 21 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– älёxölüt
Nov 21 at 13:53
@StoryTeller: What exactly makes it a bug? If
<random>is surrounded by one huge#if __cplusplus > 199711L, making it effectively empty in C++98, I'd be hard-pressed to find wording in C++98 making that a bug.– MSalters
Nov 21 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 at 14:09