Enforcing C++98/03 for clang
2
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 '18 at 13:06
αλεχολυταλεχολυτ
1,93811548
|
show 2 more comments
2
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 '18 at 13:06
αλεχολυταλεχολυτ
1,93811548
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 '18 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 '18 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– αλεχολυτ
Nov 21 '18 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 '18 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 '18 at 14:09
|
show 2 more comments
2
2
2
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 '18 at 13:06
αλεχολυταλεχολυτ
1,93811548
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 '18 at 13:06
αλεχολυταλεχολυτ
1,93811548
asked Nov 21 '18 at 13:06
αλεχολυταλεχολυτ
1,93811548
edited Nov 21 '18 at 13:07
αλεχολυτ
asked Nov 21 '18 at 13:06
αλεχολυταλεχολυτ
1,93811548
asked Nov 21 '18 at 13:06
αλεχολυταλεχολυτ
1,93811548
asked Nov 21 '18 at 13:06
αλεχολυταλεχολυτ
1,93811548
1,93811548
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 '18 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 '18 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– αλεχολυτ
Nov 21 '18 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 '18 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 '18 at 14:09
|
show 2 more comments
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 '18 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 '18 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– αλεχολυτ
Nov 21 '18 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 '18 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 '18 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 '18 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 '18 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 '18 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 '18 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– αλεχολυτ
Nov 21 '18 at 13:53
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– αλεχολυτ
Nov 21 '18 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 '18 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 '18 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 '18 at 14:09
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 '18 at 14:09
|
show 2 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
0
active
oldest
votes
0
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.
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 '18 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 '18 at 13:20
@YSC from the clang's point of view - maybe... Did clang exist in '03?
– αλεχολυτ
Nov 21 '18 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 '18 at 14:06
@MSalters - If only... wandbox.org/permlink/atmIpYn3tYY1e040
– StoryTeller
Nov 21 '18 at 14:09