From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28946 invoked by alias); 24 Nov 2004 00:05:57 -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 28913 invoked from network); 24 Nov 2004 00:05:51 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.9) by sourceware.org with SMTP; 24 Nov 2004 00:05:51 -0000 Received: (qmail 4468 invoked from network); 24 Nov 2004 00:05:51 -0000 Received: from localhost (HELO digraph.polyomino.org.uk) (joseph@127.0.0.1) by mail.codesourcery.com with DES-CBC3-SHA encrypted SMTP; 24 Nov 2004 00:05:51 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.42) id 1CWkfN-0005ie-B3; Wed, 24 Nov 2004 00:05:49 +0000 Date: Wed, 24 Nov 2004 00:32:00 -0000 From: "Joseph S. Myers" X-X-Sender: jsm28@digraph.polyomino.org.uk To: Eric Botcazou cc: gcc@gcc.gnu.org, Ziemowit Laski Subject: Re: generalized lvalues -- patch outline In-Reply-To: <200411240051.19500.ebotcazou@libertysurf.fr> Message-ID: References: <4D2CF60C-3919-11D9-8BD2-000A95BCF344@apple.com> <200411232305.56192.ebotcazou@libertysurf.fr> <200411240051.19500.ebotcazou@libertysurf.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-11/txt/msg00867.txt.bz2 On Wed, 24 Nov 2004, Eric Botcazou wrote: > http://www.kerneltraffic.org/kernel-traffic/kt20041009_276.html#3 > > compatibility between versions. I even have userland programs which do not > compile anymore with gcc-3.3 and which I don't even know how to > 'fix' (workaround ?)."> If 3.3 is the problem version, lvalue casts aren't the issue; they are still present in 3.3. (The backporting of the deprecation which was put in 3.3.4 is something I would consider dubious: though backporting a deprecation may be tempting and give users more warning, it also might break code that was working with that release series, which really should be avoided within a release series once it has first had a release: upgrading from a.b.c to a.b.c+1 should always be safe even with code using a feature that is going to go away.) -- Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/ jsm@polyomino.org.uk (personal mail) joseph@codesourcery.com (CodeSourcery mail) jsm28@gcc.gnu.org (Bugzilla assignments and CCs)