From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3441 invoked by alias); 26 Nov 2004 20:03:47 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 3242 invoked from network); 26 Nov 2004 20:03:41 -0000 Received: from unknown (HELO smtp2.fuse.net) (216.68.8.175) by sourceware.org with SMTP; 26 Nov 2004 20:03:41 -0000 Received: from gx5.fuse.net ([66.42.243.19]) by smtp2.fuse.net (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20041126200248.WZQY13140.smtp2.fuse.net@gx5.fuse.net> for ; Fri, 26 Nov 2004 15:02:48 -0500 Received: from dellpi.pinski.fam ([66.42.243.19]) by gx5.fuse.net (InterMail vG.1.00.00.00 201-2136-104-20040331) with ESMTP id <20041126200214.EEDR9958.gx5.fuse.net@dellpi.pinski.fam>; Fri, 26 Nov 2004 15:02:14 -0500 Received: from [10.0.0.80] (zhivago.i.pinski.fam [10.0.0.80]) by dellpi.pinski.fam (8.12.2/8.12.1) with ESMTP id iAQK3aVT021488; Fri, 26 Nov 2004 15:03:37 -0500 (EST) In-Reply-To: <200411262155.02799.mikael.kilpelainen@kolumbus.fi> References: <20041126191040.GD9325@ee.ethz.ch> <9C148074-3FDF-11D9-941D-000A95D692F4@physics.uc.edu> <200411262155.02799.mikael.kilpelainen@kolumbus.fi> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <416BE1A0-3FE6-11D9-941D-000A95D692F4@physics.uc.edu> Content-Transfer-Encoding: quoted-printable Cc: gcc@gcc.gnu.org From: Andrew Pinski Subject: Re: Passing temprary by reference requires copy constructor in 3.4? Date: Fri, 26 Nov 2004 21:36:00 -0000 To: =?ISO-8859-1?Q?Mikael_Kilpel=E4inen?= X-SW-Source: 2004-11/txt/msg01040.txt.bz2 On Nov 26, 2004, at 2:55 PM, Mikael Kilpel=E4inen wrote: > On Friday 26 November 2004 21:16, Andrew Pinski wrote: >> >> It does not require the copy constructor, just requires it be >> accessible. >> I would read the changes page for 3.4 which documents why this=20 >> changed. >> Mainly this is required by the C++ standard. > > Indeed, however seems that std commitee is removing the restriction.=20 > Hence I > would like to see a flag to disable the error (if there is not one=20 > already > and I am just not aware of it). I am refering to the DR 391. Why, the DR is still active so GCC is correct as of right now. If and when the DR goes to defect, we will implement the needed change. But currently GCC is following the standard. Thanks, Andrew Pinski