From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5121 invoked by alias); 18 Nov 2004 05:33:49 -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 5104 invoked from network); 18 Nov 2004 05:33:45 -0000 Received: from unknown (HELO mail-out3.apple.com) (17.254.13.22) by sourceware.org with SMTP; 18 Nov 2004 05:33:45 -0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id iAI5dmt1028263 for ; Wed, 17 Nov 2004 21:39:48 -0800 (PST) Received: from relay3.apple.com (relay3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.14) with ESMTP id ; Wed, 17 Nov 2004 21:34:22 -0800 Received: from [17.219.197.172] ([17.219.197.172]) by relay3.apple.com (8.12.11/8.12.11) with ESMTP id iAI5XgAr005152; Wed, 17 Nov 2004 21:33:42 -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 v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <68A0DBA9-3923-11D9-8BD2-000A95BCF344@apple.com> Content-Transfer-Encoding: 7bit Cc: Andrew Pinski , gcc mailing list From: Matt Austern Subject: Re: generalized lvalues Date: Thu, 18 Nov 2004 07:37:00 -0000 To: Joe Buck X-SW-Source: 2004-11/txt/msg00617.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. I hope you're right. I take the pessimistic view that there are lots of programmers who have no idea what the language definition is for the language they're using, but just throw code at the compiler until the compiler produces an executable that seems to work. So I think there may be some people who are using the cast-as-lvalue extension even if they don't know what a cast or an lvalue is. --matt