From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17271 invoked by alias); 25 May 2005 12:02:34 -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 17172 invoked by uid 22791); 25 May 2005 12:02:27 -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 12:02:27 +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 j4PC2PKK009725; Wed, 25 May 2005 08:02:25 -0400 (EDT) Received: (from ghazi@localhost) by caipclassic.rutgers.edu (8.11.6+Sun/8.10.2) id j4PC2PQ28796; Wed, 25 May 2005 08:02:25 -0400 (EDT) Date: Wed, 25 May 2005 13:38:00 -0000 From: "Kaveh R. Ghazi" Message-Id: <200505251202.j4PC2PQ28796@caipclassic.rutgers.edu> To: dj@redhat.com Subject: Re: Compiling GCC with g++: a report Cc: gcc@gcc.gnu.org References: <1116907280.9577.31.camel@localhost.localdomain> <87br71kv04.fsf@codesourcery.com> <4292C8FF.6000804@codesourcery.com> <200505250220.j4P2K9R27692@caipclassic.rutgers.edu> <200505250320.j4P3K65n002055@greed.delorie.com> X-SW-Source: 2005-05/txt/msg01362.txt.bz2 > > 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. > > Why not this? > > #ifndef __cplusplus > #pragma GCC poison class template new . . . > #endif That's limited. A new -W flag could catch not only this, but also other problems like naked void* -> FOO* conversions. E.g. IIRC, the -Wtraditional flag eventually caught over a dozen different problems. Over time this new warning flag for c/c++ intersection could be similarly refined. --Kaveh -- Kaveh R. Ghazi ghazi@caip.rutgers.edu