public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/31426] TR1 includes do not work with -std=c++0x
Date: Fri, 25 May 2007 17:12:00 -0000 [thread overview]
Message-ID: <20070525171205.3969.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31426-6353@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from pcarlini at suse dot de 2007-05-25 17:12 -------
(In reply to comment #2)
> I don't think support for C++0x precludes support for TR1. They coexist very
> well, especially because TR1 was designed to be compatible with C++0x. For
> example, C++0x-conforming implementations of the TR1 facilities also meet the
> requirements of TR1.
Hi Doug. Upon Benjamin' invitation, I'm working on this issue, with the initial
goal of making progress on the C++0x version of type_traits (for example, it
will exploit more front-end builtins).
Now, however, I do not agree completely with your statement above: certainly,
for example, a C++0x-conforming type_traits doesn't meet the requirements of
TR1. That, in turn, sheds doubts to the very point that TR1 facilities must be
available in C++0x mode: if the user does an using from namespace tr1 to
namespace std of a tr1 facility which finds a same-named, but incompatible
facility (i.e., implementing different semantics) in namespace std, which one
is supposed to "survive"?
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pcarlini at suse dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31426
next prev parent reply other threads:[~2007-05-25 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 14:32 [Bug libstdc++/31426] New: " dgregor at gcc dot gnu dot org
2007-04-02 15:18 ` [Bug libstdc++/31426] " rguenth at gcc dot gnu dot org
2007-04-02 15:33 ` dgregor at gcc dot gnu dot org
2007-04-02 16:26 ` rguenth at gcc dot gnu dot org
2007-04-06 8:33 ` bkoz at gcc dot gnu dot org
2007-05-25 17:12 ` pcarlini at suse dot de [this message]
2007-05-25 17:39 ` pcarlini at suse dot de
2007-05-31 23:38 ` paolo at gcc dot gnu dot org
2007-06-01 8:49 ` pcarlini at suse dot de
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=20070525171205.3969.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).