public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/14875] When using 'or' keyword, the error message speaks of a '||' token
Date: Sun, 28 Jan 2007 02:41:00 -0000	[thread overview]
Message-ID: <20070128024136.19202.qmail@sourceware.org> (raw)
In-Reply-To: <bug-14875-8295@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from manu at gcc dot gnu dot org  2007-01-28 02:41 -------
(In reply to comment #7)
> I seem to recall that when Giovanni worked on these digraph thingies,
> it was pointed out that our CPP is able to mark a pp-token whether it
> is a digraph or not.
> 

Actually, it is marked as token->flags & NAMED_OP. This can be easily tested.
However, the way the C++ front-end handles parser errors makes that totally
useless. Once we reach c-common.c (c_parse_error), the actual cp_token is lost
and we only keep the type. Also, it seems that it should be using
cpp_token_as_text rather than cpp_type2name. However, the change does not seem
trivial at all.

Unless someone decides to fix the whole C++ parser error handling, this and PR
28152 won't be fixed.

Any brave volunteer?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14875


       reply	other threads:[~2007-01-28  2:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-14875-8295@http.gcc.gnu.org/bugzilla/>
2007-01-28  2:41 ` manu at gcc dot gnu dot org [this message]
2007-01-28  4:11 ` gdr at cs dot tamu dot edu
2007-02-01 12:16 ` manu at gcc dot gnu dot org
2007-11-22  8:39 ` spiridenok at tut dot by
2009-02-07 20:29 ` manu at gcc dot gnu dot org
2009-04-22 15:32 ` manu at gcc dot gnu dot org
2009-04-22 15:33 ` manu at gcc dot gnu dot org
2004-04-07 11:58 [Bug c++/14875] New: No or in function names allowed j dot werner at physik dot uni-stuttgart dot de
2004-04-07 13:23 ` [Bug c++/14875] When using 'or' keyword, the error message speaks of a '||' token giovannibajo at libero dot it
2004-04-07 13:31 ` pinskia at gcc dot gnu dot org
2004-04-08 18:34 ` bangerth at dealii dot org
2004-04-08 18:53   ` Zack Weinberg
2004-04-08 18:53 ` zack at codesourcery dot com
2004-04-08 19:54 ` gdr at integrable-solutions dot net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070128024136.19202.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).