From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21180 invoked by alias); 18 Nov 2004 18:19:30 -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 21157 invoked from network); 18 Nov 2004 18:19:23 -0000 Received: from unknown (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org with SMTP; 18 Nov 2004 18:19:23 -0000 Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id iAIIPuj3026461 for ; Thu, 18 Nov 2004 10:25:56 -0800 (PST) Received: from relay3.apple.com (relay3.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.3.14) with ESMTP id ; Thu, 18 Nov 2004 10:19:22 -0800 Received: from [17.201.20.87] (mrs2.apple.com [17.201.20.87]) by relay3.apple.com (8.12.11/8.12.11) with ESMTP id iAIIJK2D006692; Thu, 18 Nov 2004 10:19:20 -0800 (PST) In-Reply-To: <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> <20041117212847.A26376@synopsys.com> Mime-Version: 1.0 (Apple Message framework v679) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6F5FC748-7BBD-44B9-8DDC-246949F16102@apple.com> Cc: Matt Austern , Andrew Pinski , gcc mailing list Content-Transfer-Encoding: 7bit From: Mike Stump Subject: Re: generalized lvalues Date: Thu, 18 Nov 2004 18:28:00 -0000 To: Joe Buck X-SW-Source: 2004-11/txt/msg00630.txt.bz2 On Nov 17, 2004, at 9:28 PM, Joe Buck wrote: > 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. Just a random data point, 58 out of 1252 (4.6%) projects failed to build because of it.