From: "Jan Kundrát" <jkt@gentoo.org>
To: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] How to support C++11 in libraries?
Date: Fri, 20 Dec 2013 13:45:37 +0100 [thread overview]
Message-ID: <e97d92da-adfd-4a4e-9eb3-fa1958ff5f63@gentoo.org> (raw)
In-Reply-To: <1479290.p0qqMGJcP8@sed-notebook>
On Friday, 20 December 2013 12:56:43 CEST, Sven Eden wrote:
> And no, the languages are _not_ "source-incompatible". That would be a
> scandal!
You might argue about this, but that doesn't change these facts. This is
absolutely valid C++98 program:
jkt@svist ~ $ cat foo.cpp
int main() {
auto int foo;
return 0;
}
jkt@svist ~ $ g++ -std=c++98 -pedantic foo.cpp
jkt@svist ~ $ echo $?
0
...which will *not* build under the C++11 mode:
jkt@svist ~ $ g++ -std=c++0x foo.cpp
foo.cpp: In function ‘int main()’:
foo.cpp:2:14: error: two or more data types in declaration of ‘foo’
Yes, -Wc++0x-compat warns about this, yes, it's included in -Wall, but it
does not change the fact that there *is* code out there which does conform
to C++98 standard, does *not* try to "outsmart the compiler", and which
will not build in the C++11 mode. Do we really have to be having this
discussion?
Cheers,
Jan
next prev parent reply other threads:[~2013-12-20 12:45 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 7:54 [gentoo-dev] How to support C++11 in libraries? Michał Górny
2013-12-18 8:20 ` "C. Bergström"
2013-12-18 18:07 ` Michał Górny
2013-12-18 13:58 ` heroxbd
2013-12-18 16:29 ` Jan Kundrát
2013-12-18 16:37 ` "C. Bergström"
2013-12-18 16:50 ` Jan Kundrát
2013-12-18 17:05 ` "C. Bergström"
2013-12-18 17:33 ` Jan Kundrát
2013-12-18 17:47 ` Kent Fredric
2013-12-18 17:56 ` "C. Bergström"
2013-12-19 1:45 ` heroxbd
2013-12-19 8:20 ` Michał Górny
2013-12-19 8:28 ` "C. Bergström"
2013-12-19 8:35 ` Michał Górny
2013-12-19 8:44 ` "C. Bergström"
2013-12-19 12:28 ` Jan Kundrát
2013-12-19 8:45 ` Jan Kundrát
2013-12-19 8:47 ` Georg Rudoy
2013-12-18 17:49 ` "C. Bergström"
2013-12-18 18:28 ` Georg Rudoy
2013-12-19 1:41 ` heroxbd
2013-12-19 8:43 ` Jan Kundrát
2013-12-19 9:18 ` Michał Górny
2013-12-19 13:47 ` heroxbd
2013-12-19 14:46 ` Michał Górny
2013-12-19 15:12 ` heroxbd
2013-12-19 16:56 ` Ciaran McCreesh
2013-12-19 15:17 ` Jan Kundrát
2013-12-19 16:29 ` vivo75
2013-12-19 16:51 ` Jan Kundrát
2013-12-21 2:36 ` [gentoo-dev] " Ryan Hill
2013-12-18 18:15 ` [gentoo-dev] " Michał Górny
2013-12-18 20:58 ` [gentoo-dev] " Martin Vaeth
2013-12-19 2:01 ` [gentoo-dev] " heroxbd
2013-12-18 14:27 ` Ian Stakenvicius
2013-12-18 18:10 ` Anthony G. Basile
2013-12-18 18:28 ` Ian Stakenvicius
2013-12-19 8:58 ` Sven Eden
2013-12-19 9:07 ` Michał Górny
2013-12-19 15:00 ` Ian Stakenvicius
2013-12-19 15:23 ` Jan Kundrát
2013-12-19 16:00 ` Anthony G. Basile
2013-12-20 9:00 ` [gentoo-dev] " Martin Vaeth
2013-12-20 12:35 ` [gentoo-dev] " Jan Kundrát
2013-12-20 17:35 ` [gentoo-dev] " Martin Vaeth
2013-12-20 11:56 ` [gentoo-dev] " Sven Eden
2013-12-20 12:45 ` Jan Kundrát [this message]
2013-12-20 12:54 ` Georg Rudoy
2013-12-20 17:49 ` [gentoo-dev] " Martin Vaeth
2013-12-20 15:10 ` [gentoo-dev] " Ian Stakenvicius
2013-12-19 15:51 ` Anthony G. Basile
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e97d92da-adfd-4a4e-9eb3-fa1958ff5f63@gentoo.org \
--to=jkt@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox