public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109936] error: extended character ≠ is not valid in an identifier
Date: Tue, 23 May 2023 09:06:34 +0000 [thread overview]
Message-ID: <bug-109936-4-YDvpLTgROn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109936-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936
--- Comment #19 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andreas Schwab from comment #10)
> It is a valid preprocessing token ("non-whitespace character that cannot be
> one of the above").
Ah right, yes. It's a preprocessing token, but is never converted to a token,
so doesn't need to be a keyword, identifier etc.
next prev parent reply other threads:[~2023-05-23 9:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 19:58 [Bug c++/109936] New: " adam at wozniakconsulting dot com
2023-05-22 20:04 ` [Bug c++/109936] " pinskia at gcc dot gnu.org
2023-05-22 20:06 ` pinskia at gcc dot gnu.org
2023-05-22 20:06 ` pinskia at gcc dot gnu.org
2023-05-22 20:16 ` adam at wozniakconsulting dot com
2023-05-22 20:17 ` redi at gcc dot gnu.org
2023-05-22 20:26 ` redi at gcc dot gnu.org
2023-05-22 20:29 ` pinskia at gcc dot gnu.org
2023-05-22 20:52 ` adam at wozniakconsulting dot com
2023-05-22 20:58 ` redi at gcc dot gnu.org
2023-05-22 21:14 ` schwab@linux-m68k.org
2023-05-22 21:20 ` jakub at gcc dot gnu.org
2023-05-22 23:36 ` adam at wozniakconsulting dot com
2023-05-22 23:43 ` adam at wozniakconsulting dot com
2023-05-22 23:47 ` adam at wozniakconsulting dot com
2023-05-23 0:39 ` adam at wozniakconsulting dot com
2023-05-23 1:54 ` pinskia at gcc dot gnu.org
2023-05-23 1:55 ` pinskia at gcc dot gnu.org
2023-05-23 8:01 ` schwab@linux-m68k.org
2023-05-23 9:06 ` redi at gcc dot gnu.org [this message]
2023-05-23 15:31 ` adam at wozniakconsulting dot com
2023-05-23 15:38 ` adam at wozniakconsulting dot com
2023-05-23 15:40 ` adam at wozniakconsulting dot com
2023-05-23 16:00 ` redi at gcc dot gnu.org
2023-05-23 17:23 ` adam at wozniakconsulting dot com
2023-05-23 17:36 ` joseph at codesourcery dot com
2023-05-23 18:05 ` adam at wozniakconsulting dot com
2023-11-24 15:41 ` pinskia at gcc dot gnu.org
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=bug-109936-4-YDvpLTgROn@http.gcc.gnu.org/bugzilla/ \
--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).