From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19952 invoked by alias); 1 Feb 2007 12:16:33 -0000 Received: (qmail 19841 invoked by uid 48); 1 Feb 2007 12:16:13 -0000 Date: Thu, 01 Feb 2007 12:16:00 -0000 Message-ID: <20070201121613.19840.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/14875] When using 'or' keyword, the error message speaks of a '||' token In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "manu at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-02/txt/msg00042.txt.bz2 ------- Comment #10 from manu at gcc dot gnu dot org 2007-02-01 12:16 ------- (In reply to comment #9) > Subject: Re: When using 'or' keyword, the error message speaks of a '||' token > > "manu at gcc dot gnu dot org" writes: > > | Unless someone decides to fix the whole C++ parser error handling, > | this and PR 28152 won't be fixed. > > I would refrain from sweeping generalization like the above. > Diagnostics with carret do not necessary require "fixing" the parser; > and, yet they can be implemented in a way that resolves this issue. > I am not talking about the parser itself but about the way it handles errors. token->flags gets lost inside the machinery launched by a call to cp_parse_error. So I would like to know how you think this can be implemented (honestly!), perhaps I missed some other way to distinguish the 'or' token from '||'. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14875