From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 5/5] Handle non-ASCII identifiers in Ada
Date: Tue, 01 Mar 2022 17:17:57 +0200 [thread overview]
Message-ID: <838rttln16.fsf@gnu.org> (raw)
In-Reply-To: <87czj5locm.fsf@tromey.com> (message from Tom Tromey on Tue, 01 Mar 2022 07:49:29 -0700)
> From: Tom Tromey <tromey@adacore.com>
> Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
> Date: Tue, 01 Mar 2022 07:49:29 -0700
>
> These were in Unicode back in 2001.
>
> Eli> Or maybe we should document what is the
> Eli> oldest version of Python that currently suits the needs?
>
> Most people shouldn't run this script. The output is checked in. And
> if they do and get wildly different results, that will be caught in
> review.
>
> Of course, it won't really matter, because you can't really write an Ada
> program -- at least, not using GNAT -- that uses anything after 2001
> anyway. This covers all the Python versions that are in normal use.
>
> For example Python 2.7, the oldest one I have around (and for which gdb
> is going to drop support soon anyway):
>
> >>> import unicodedata
> >>> unicodedata.unidata_version
> '5.2.0'
>
> This version of the data comes from 2009, plenty new enough.
Ok, I guess there's no real problem, then.
Thanks.
next prev parent reply other threads:[~2022-03-01 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 18:32 [PATCH 0/5] " Tom Tromey
2022-02-28 18:33 ` [PATCH 1/5] Simplify a regular expression in ada-lex.l Tom Tromey
2022-02-28 18:33 ` [PATCH 2/5] Don't pre-size result string in ada_decode Tom Tromey
2022-02-28 18:33 ` [PATCH 3/5] Let phex and phex_nz handle sizeof_l==1 Tom Tromey
2022-03-01 14:26 ` Simon Marchi
2022-03-01 14:32 ` Tom Tromey
2022-02-28 18:33 ` [PATCH 4/5] Define HOST_UTF32 in charset.h Tom Tromey
2022-02-28 18:33 ` [PATCH 5/5] Handle non-ASCII identifiers in Ada Tom Tromey
2022-02-28 18:59 ` Eli Zaretskii
2022-02-28 20:59 ` Tom Tromey
2022-03-01 3:28 ` Eli Zaretskii
2022-03-01 14:49 ` Tom Tromey
2022-03-01 15:17 ` Eli Zaretskii [this message]
2022-03-01 15:33 ` Tom Tromey
2022-03-07 14:52 ` [PATCH 0/5] " Tom Tromey
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=838rttln16.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).