From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9871 invoked by alias); 21 Apr 2002 10:47:25 -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 9863 invoked from network); 21 Apr 2002 10:47:24 -0000 Received: from unknown (HELO mail.enyo.de) (212.9.189.162) by sources.redhat.com with SMTP; 21 Apr 2002 10:47:24 -0000 Received: from [212.9.189.171] (helo=deneb.enyo.de) by mail.enyo.de with esmtp (Exim 3.34 #2) id 16zEsQ-0004eR-00; Sun, 21 Apr 2002 12:47:26 +0200 Received: from fw by deneb.enyo.de with local (Exim 3.34 #4) id 16zEsM-0005Ah-00; Sun, 21 Apr 2002 12:47:22 +0200 To: kgardas@objectsecurity.com Cc: gcc@gcc.gnu.org Subject: Re: gcc 2.95.x interesting c++ parser error (bug). References: From: Florian Weimer Date: Sun, 21 Apr 2002 04:32:00 -0000 In-Reply-To: (Karel Gardas's message of "Sat, 20 Apr 2002 16:53:10 +0200 (CEST)") Message-ID: <87znzx9vlx.fsf@deneb.enyo.de> User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-04/txt/msg01038.txt.bz2 Karel Gardas writes: > because it takes me some time to find exact place in my sources which > cause this bug (these sources are of course perfectly OK with gcc 3.1). The sources aren't perfectly okay. You must not use identifiers with two leading underscores (see section 17.4.3.1.2 in ISO/IEC 14882).