From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2201 invoked by alias); 18 Nov 2004 05:28:55 -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 2148 invoked from network); 18 Nov 2004 05:28:48 -0000 Received: from unknown (HELO boden.synopsys.com) (198.182.44.79) by sourceware.org with SMTP; 18 Nov 2004 05:28:48 -0000 Received: from maiden.synopsys.com (maiden.synopsys.com [146.225.100.170]) by boden.synopsys.com (Postfix) with ESMTP id A73BEDB9C; Wed, 17 Nov 2004 21:28:13 -0800 (PST) Received: from piper.synopsys.com (localhost [127.0.0.1]) by maiden.synopsys.com (8.9.1/8.9.1) with ESMTP id VAA24552; Wed, 17 Nov 2004 21:28:47 -0800 (PST) Received: (from jbuck@localhost) by piper.synopsys.com (8.11.6/8.11.6) id iAI5SlH27022; Wed, 17 Nov 2004 21:28:47 -0800 X-Authentication-Warning: piper.synopsys.com: jbuck set sender to Joe.Buck@synopsys.com using -f Date: Thu, 18 Nov 2004 07:15:00 -0000 From: Joe Buck To: Matt Austern Cc: Andrew Pinski , gcc mailing list Subject: Re: generalized lvalues Message-ID: <20041117212847.A26376@synopsys.com> References: <8AD5AEEF-3914-11D9-8BD2-000A95BCF344@apple.com> <78169FF3-3916-11D9-AEB4-000A95D692F4@physics.uc.edu> <4D2CF60C-3919-11D9-8BD2-000A95BCF344@apple.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <4D2CF60C-3919-11D9-8BD2-000A95BCF344@apple.com>; from austern@apple.com on Wed, Nov 17, 2004 at 08:21:21PM -0800 X-SW-Source: 2004-11/txt/msg00616.txt.bz2 On Wed, Nov 17, 2004 at 08:21:21PM -0800, Matt Austern wrote: > Yep, and I'm still not arguing against removing it. I'm just asking > for help in collecting a list of the reasons why we chose to get rid of > it. I don't think this discussion will go away, and having that list > will be helpful. I think a number of us will be asked: (a) why did > this extension disappear; and (b) how should I change my code to cope > with the disappearance. I'd like to be prepared with answers to those > questions. I doubt if you will get the flood of questions you anticipate, because few people even knew that the extension was there. It is possible that someone has a production program that is not valid C++ that will now break, but if this happens we just tell them how to fix the program.