public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dgregor at gcc dot gnu dot org" <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: Mon, 02 Apr 2007 15:33:00 -0000 [thread overview] Message-ID: <20070402153251.9180.qmail@sourceware.org> (raw) In-Reply-To: <bug-31426-6353@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from dgregor at gcc dot gnu dot org 2007-04-02 16:32 ------- I don't think it is a feature. In C++0x mode, if one includes <tuple>, one should get std::tuple. That's what the C++0x working paper says. In any mode, if one includes <tr1/tuple>, one should get std::tr1::tuple. That's what TR1 says (well, TR1 might say that you get std::tr1::tuple from including <tuple>; different vendors have done different things, here). 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. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31426
next prev parent reply other threads:[~2007-04-02 15:33 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 [this message] 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 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=20070402153251.9180.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: linkBe 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).