From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9228 invoked by alias); 2 Apr 2007 15:33:03 -0000 Received: (qmail 9181 invoked by uid 48); 2 Apr 2007 15:32:51 -0000 Date: Mon, 02 Apr 2007 15:33:00 -0000 Message-ID: <20070402153251.9180.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/31426] TR1 includes do not work with -std=c++0x In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dgregor at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-04/txt/msg00080.txt.bz2 ------- 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 , one should get std::tuple. That's what the C++0x working paper says. In any mode, if one includes , one should get std::tr1::tuple. That's what TR1 says (well, TR1 might say that you get std::tr1::tuple from including ; 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