From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 5/5] Handle non-ASCII identifiers in Ada
Date: Mon, 28 Feb 2022 13:59:37 -0700 [thread overview]
Message-ID: <87lexulnba.fsf@tromey.com> (raw)
In-Reply-To: <83y21ulsuo.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 28 Feb 2022 20:59:59 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Mon, 28 Feb 2022 11:33:04 -0700
>> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
>> Cc: Tom Tromey <tromey@adacore.com>
>>
>> +for c in range(0, 0x10FFFF):
>> + process_codepoint(c)
Eli> This script assumes that the version of Python which will run it is
Eli> up-to-date with the latest Unicode Character Database (UCD), right?
Eli> Is that a good assumption? Wouldn't it be better to process the UCD
Eli> from the latest Unicode Standard directly?
Ordinarily, yes, but in practice the Ada compiler uses quite old data,
and so whatever is provided by a recent-ish Python is more than good
enough.
If the Ada compiler is changed, I'll update the script. I suspect this
won't happen, though.
Tom
next prev parent reply other threads:[~2022-02-28 20:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 18:32 [PATCH 0/5] " Tom Tromey via Gdb-patches
2022-02-28 18:33 ` [PATCH 1/5] Simplify a regular expression in ada-lex.l Tom Tromey via Gdb-patches
2022-02-28 18:33 ` [PATCH 2/5] Don't pre-size result string in ada_decode Tom Tromey via Gdb-patches
2022-02-28 18:33 ` [PATCH 3/5] Let phex and phex_nz handle sizeof_l==1 Tom Tromey via Gdb-patches
2022-03-01 14:26 ` Simon Marchi via Gdb-patches
2022-03-01 14:32 ` Tom Tromey via Gdb-patches
2022-02-28 18:33 ` [PATCH 4/5] Define HOST_UTF32 in charset.h Tom Tromey via Gdb-patches
2022-02-28 18:33 ` [PATCH 5/5] Handle non-ASCII identifiers in Ada Tom Tromey via Gdb-patches
2022-02-28 18:59 ` Eli Zaretskii via Gdb-patches
2022-02-28 20:59 ` Tom Tromey via Gdb-patches [this message]
2022-03-01 3:28 ` Eli Zaretskii via Gdb-patches
2022-03-01 14:49 ` Tom Tromey via Gdb-patches
2022-03-01 15:17 ` Eli Zaretskii via Gdb-patches
2022-03-01 15:33 ` Tom Tromey via Gdb-patches
2022-03-07 14:52 ` [PATCH 0/5] " Tom Tromey via Gdb-patches
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=87lexulnba.fsf@tromey.com \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=tromey@adacore.com \
/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