From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27565 invoked by alias); 30 Jul 2002 15:56:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 27552 invoked by uid 71); 30 Jul 2002 15:56:01 -0000 Date: Tue, 30 Jul 2002 08:56:00 -0000 Message-ID: <20020730155601.27551.qmail@sources.redhat.com> To: gdr@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Neil Booth Subject: Re: c++/7440: parse error on valid C++ code (parse error before `&&' token) Reply-To: Neil Booth X-SW-Source: 2002-07/txt/msg00787.txt.bz2 List-Id: The following reply was made to PR c++/7440; it has been noted by GNATS. From: Neil Booth To: gdr@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gsd@dolphin.fr, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/7440: parse error on valid C++ code (parse error before `&&' token) Date: Tue, 30 Jul 2002 16:49:41 +0100 gdr@gcc.gnu.org wrote:- > Synopsis: parse error on valid C++ code (parse error before `&&' token) > > Responsible-Changed-From-To: unassigned->gdr > Responsible-Changed-By: gdr > Responsible-Changed-When: Tue Jul 30 01:05:53 2002 > Responsible-Changed-Why: > Analyzed. > State-Changed-From-To: open->closed > State-Changed-By: gdr > State-Changed-When: Tue Jul 30 01:05:53 2002 > State-Changed-Why: > Not a bug. We really need to use CPP to print tokens, the diagnostic in this case is awful, and quite misleading. Neil.