From: Joe Buck <Joe.Buck@synopsys.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>,
James Y Knight <foom@fuhm.net>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: Long-term plan for C++98/C++11 incompatibility
Date: Sat, 08 Oct 2011 06:39:00 -0000 [thread overview]
Message-ID: <59662D5BB74CD84D9FA8E6491ADB51A7DEAE4E3D@US01WXMBX1.internal.synopsys.com> (raw)
In-Reply-To: <CAAiZkiBRjZwTDvH=7mgog1dy5mv09L3O9x5oup4qYV1Pb8KayQ@mail.gmail.com>
On Fri, Oct 7, 2011 at 5:24 PM, James Y Knight <foom@fuhm.net> wrote:
> I guess to start, it would have been nice if there was a big warning on
> http://gcc.gnu.org/projects/cxx0x.html telling me not to use c++0x mode
> unless there are no objects compiled with c++98 linked into the same
> executable.
Gabriel Dos Reis [gdr@integrable-solutions.net] wrote:
> I was under the impression c++0x was explicitly documented as experimental.
Yes. But I hope that some thought is devoted to figuring out how this problem
can be dealt with when c++11 support is transitioned to a fully supported feature.
Eventually there would need to be one libstdc++ that programs link against and
run whether they use c++98 or c++11. I would expect there to be restrictions,
but it's a problem that eventually needs to be tackled.
next prev parent reply other threads:[~2011-10-08 2:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 23:44 James Y Knight
2011-10-08 2:17 ` Jonathan Wakely
2011-10-08 2:35 ` Jonathan Wakely
2011-10-08 4:57 ` Gabriel Dos Reis
2011-10-08 6:39 ` Joe Buck [this message]
2011-10-08 7:34 ` Gabriel Dos Reis
2011-10-11 9:41 ` Joe Buck
2011-10-11 10:53 ` Gabriel Dos Reis
2011-12-15 18:04 ` Jeffrey Yasskin
2012-01-05 18:35 ` Jason Merrill
2012-01-05 18:39 ` Jason Merrill
2012-01-05 18:55 ` Joe Buck
2012-01-05 22:23 ` Jason Merrill
2011-10-08 7:35 ` Miles Bader
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=59662D5BB74CD84D9FA8E6491ADB51A7DEAE4E3D@US01WXMBX1.internal.synopsys.com \
--to=joe.buck@synopsys.com \
--cc=foom@fuhm.net \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).