public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100977] [C++23] Implement C++ Identifier Syntax using Unicode Standard Annex 31
Date: Wed, 04 Aug 2021 18:34:59 +0000 [thread overview]
Message-ID: <bug-100977-4-7VZrUFjAVR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100977-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100977
--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 4 Aug 2021, jakub at gcc dot gnu.org via Gcc-bugs wrote:
> plus various changes in the check_nfc function.
> So, the first question is if the C11/N11/C99 etc. stuff should use Unicode 4.1
> (or what was used when it was generated) tables and only CXX20/NXX20 should use
> Unicode 13.0 tables (what about NFC/NKC?), or if it is ok to just regenerate
> everything using Unicode 13.0 files, add parsing of the
> DerivedCoreProperties.txt file too (and pick XID_Start and XID_Continue
> properties there, throw away everything < 0x80 and otherwise compute CXX20 flag
> as XID_Continue and NXX20 flag as XID_Continue \ XID_Start.
I think it's fine for the normalization tests for older standard versions
to use the latest Unicode version, so changing each time we update from
newer Unicode data (as per
<https://gcc.gnu.org/legacy-ml/gcc-patches/2013-11/msg01901.html> I used
Unicode 6.3.0 at that time).
A trickier question is whether the XID_Start and XID_Continue sets of
characters used for C++23 are meant to be fixed to a particular Unicode
version (possibly updated for future C++ versions) or whether the set used
for C++23 is meant to be updated for each future Unicode release as it
comes out.
(Note also that identifiers not in NFC become ill-formed, i.e.
-Wnormalized=nfc needs to be a pedwarn for C++23.)
next prev parent reply other threads:[~2021-08-04 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 18:15 [Bug c++/100977] New: " jason at gcc dot gnu.org
2021-06-08 18:19 ` [Bug c++/100977] " mpolacek at gcc dot gnu.org
2021-08-04 13:39 ` jakub at gcc dot gnu.org
2021-08-04 14:08 ` jakub at gcc dot gnu.org
2021-08-04 16:14 ` jakub at gcc dot gnu.org
2021-08-04 18:34 ` joseph at codesourcery dot com [this message]
2021-08-04 18:40 ` jakub at gcc dot gnu.org
2021-08-04 19:06 ` ubizjak at gmail dot com
2021-08-04 19:20 ` jakub at gcc dot gnu.org
2021-08-04 19:25 ` ubizjak at gmail dot com
2021-08-05 10:17 ` jakub at gcc dot gnu.org
2021-08-05 15:34 ` cvs-commit at gcc dot gnu.org
2021-08-05 15:35 ` cvs-commit at gcc dot gnu.org
2021-09-01 20:37 ` cvs-commit at gcc dot gnu.org
2021-09-01 20:38 ` jakub at gcc dot gnu.org
2021-11-30 8:51 ` cvs-commit at gcc dot gnu.org
2021-12-01 9:22 ` cvs-commit 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-100977-4-7VZrUFjAVR@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).