From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 638 invoked by alias); 2 May 2003 14:36:00 -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 624 invoked by uid 71); 2 May 2003 14:36:00 -0000 Date: Fri, 02 May 2003 14:36:00 -0000 Message-ID: <20030502143600.623.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Giovanni Bajo" Subject: Re: c++/10603: [3.4 regression] [new parser] failing to print problematic token upon parse error Reply-To: "Giovanni Bajo" X-SW-Source: 2003-05/txt/msg00136.txt.bz2 List-Id: The following reply was made to PR c++/10603; it has been noted by GNATS. From: "Giovanni Bajo" To: "Gerald Pfeifer" , , , , Cc: Subject: Re: c++/10603: [3.4 regression] [new parser] failing to print problematic token upon parse error Date: Fri, 2 May 2003 16:28:12 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10603 Let me add that this is not restricted to this very specific case. The new parser surely needs work in error reporting, because I could post endless regressions I found on this regard. Giovanni Bajo