From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12545 invoked by alias); 25 May 2005 02:20:43 -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 12452 invoked by uid 22791); 25 May 2005 02:20:16 -0000 Received: from caip.rutgers.edu (HELO caip.rutgers.edu) (128.6.236.10) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 25 May 2005 02:20:16 +0000 Received: from caipclassic.rutgers.edu (caipclassic.rutgers.edu [128.6.237.54]) by caip.rutgers.edu (8.13.3+Sun/8.13.3) with ESMTP id j4P2K9vG022086; Tue, 24 May 2005 22:20:13 -0400 (EDT) Received: (from ghazi@localhost) by caipclassic.rutgers.edu (8.11.6+Sun/8.10.2) id j4P2K9R27692; Tue, 24 May 2005 22:20:09 -0400 (EDT) Date: Wed, 25 May 2005 03:45:00 -0000 From: "Kaveh R. Ghazi" Message-Id: <200505250220.j4P2K9R27692@caipclassic.rutgers.edu> To: mark@codesourcery.com Subject: Re: Compiling GCC with g++: a report Cc: dberlin@dberlin.org, gcc@gcc.gnu.org, gdr@integrable-solutions.net, jason@redhat.com, zack@codesourcery.com References: <1116907280.9577.31.camel@localhost.localdomain> <87br71kv04.fsf@codesourcery.com> <4292C8FF.6000804@codesourcery.com> X-SW-Source: 2005-05/txt/msg01348.txt.bz2 > > unrestricted use of C++ keywords; declaring structure fields with > > the same name as a structure tag in scope. > > I don't think we should be reverting patches that fall afoul of these > last two, even if they break Gaby's build-with-a-C++-compiler > builds. But, I would tend to accept patches from Gaby to fix such > problems. This reminds me of the last time we were coding to two C-family variants, named K&R vs ISO. I had improved -Wtraditional to the point where it caught most problems, and we had macros (PARAMS, etc) to cover most other cases. Now we have e.g. XNEW* and all we need is a new -W* flag to catch things like using C++ keywords and it should be fairly automatic to keep incompatibilities out of the sources. IMHO Gaby should volunteer to write the new -W flag, it'll be easier for him than fixing breakage after the fact. --Kaveh -- Kaveh R. Ghazi ghazi@caip.rutgers.edu