From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18537 invoked by alias); 23 Nov 2004 15:58:12 -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 18478 invoked from network); 23 Nov 2004 15:58:03 -0000 Received: from unknown (HELO Cantor.suse.de) (195.135.220.2) by sourceware.org with SMTP; 23 Nov 2004 15:58:03 -0000 Received: from hermes.suse.de (hermes-ext.suse.de [195.135.221.8]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by Cantor.suse.de (Postfix) with ESMTP id E8BF91159B6E; Tue, 23 Nov 2004 16:58:02 +0100 (CET) Date: Tue, 23 Nov 2004 16:12:00 -0000 From: Michael Matz To: Gabriel Dos Reis Cc: Daniel Berlin , Nathan Sidwell , Ziemowit Laski , Steve Naroff , gcc mailing list , Matt Austern , Joe Buck , Andrew Pinski , Mike Stump Subject: Re: generalized lvalues -- patch outline In-Reply-To: Message-ID: References: <4D2CF60C-3919-11D9-8BD2-000A95BCF344@apple.com> <20041117212847.A26376@synopsys.com> <6F5FC748-7BBD-44B9-8DDC-246949F16102@apple.com> <20041118102741.A8347@synopsys.com> <77E8D36A-C0C2-4B03-964C-BEE0FE7BBBC3@apple.com> <98C86CD4-39E2-11D9-B2D5-000A95BCF344@apple.com> <20041119170011.A30410@synopsys.com> <9E6AD708-3A93-11D9-9070-000D9330C50E@apple.com> <20041119174042.A1311@synopsys.com> <90DC5074-3A96-11D9-9070-000D9330C50E@apple.com> <9CD04F70-3CC6-11D9-B847-000D9330C50E@apple.com> <41A253A2.1050205@codesourcery.com> <24BB97A2-3CD3-11D9-B847-000D9330C50E@apple.com> <41A30346.8050602@codesourcery.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-11/txt/msg00821.txt.bz2 Hi, On Tue, 23 Nov 2004, Gabriel Dos Reis wrote: > Michael Matz writes: > > [...] > > | The only C++ packages in which I see this is alsamixergui, chasen, > | knights, libebml and licq, so I personally would be thankful already for > | having such extension only in C. > > Such C++ prckages can use reinterpret_cast<>. > > C packages can use dedicated macros, if they really think the need > that sheating. My point in the whole discussion is to avoid having to change 50+ packages. If I'm (or whoever else is) going to fix them anyway, I can see multiple ways. So you suggesting some of those ways misses my point. > | Practically speaking 4.0 is currently strictly less usefull in some > | aspects for the average C programmer. > > Well, you and I have different notions of "average programmer". Yes. Perhaps because I have to deal with many packages built by GCC my view of the average programmer is skewed to one side, because it's natural that I only see examples of how strange things programmers do. Nobody calls me because his package compiles ;-) > Probably, this sort of situations probably happen because some people > have been encouraged in conceiving programming as an activity of > throwing random codes to the compiler and see what happens. Possible. This is one of the ways to learn programming. And despite what the language standard says, to my eyes "(T*)p++" looks like a natural way to write p+=sizeof(T), so I'm somewhat sympathetic to programmers using this construct. Ciao, Michael.