From: 張俊芝 <zjz@zjz.name>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: support C/C++ identifiers named with non-ASCII characters
Date: Tue, 22 May 2018 17:31:00 -0000 [thread overview]
Message-ID: <e4dfac0d-4177-c63c-1f28-a2707a489e3e@zjz.name> (raw)
In-Reply-To: <f69cbb32-8973-095c-ed93-9c80fed6db9a@redhat.com>
Pedro Alves æ¼ 2018/5/22 ä¸å11:17 寫é:
>>
>> I found the patch. Let me rebase it and send it / post it. It'll
>> be easier to just look at the patch.
>
> Here it is. So this is reusing the same logic added to
> cp-name-parser.y, in the C/C++ expression parser as well.
>
I read through your code. If I understand it correctly, you keep all the
valid ASCII characters, and treat all non-ASCII characters "as valid".
This is pretty much the same thing as I did. The only difference is that
I blacklist invalid ASCII characters and you whitelist valid ASCII
characters. But we both "validate" all the non-ASCII characters.
But I think your code seems better than mine because it updates and
reuses some common code. So I think I can abondon my patch and the
unfinished test case.
next prev parent reply other threads:[~2018-05-22 15:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 9:54 張俊芝
2018-05-21 14:21 ` Simon Marchi
2018-05-21 15:27 ` Paul.Koning
2018-05-21 16:16 ` Eli Zaretskii
2018-05-21 18:34 ` Paul.Koning
[not found] ` <83tvr0ev0p.fsf@gnu.org>
2018-05-21 19:25 ` Paul.Koning
2018-05-21 20:43 ` Joseph Myers
2018-05-22 10:31 ` 張俊芝
2018-05-22 8:34 ` 張俊芝
[not found] ` <1b915196-3e97-4892-7426-be4211fe7889@zjz.name>
2018-05-21 18:00 ` 張俊芝
2018-05-21 18:03 ` 張俊芝
2018-05-21 18:14 ` Matt Rice
2018-05-22 7:06 ` 張俊芝
2018-05-22 14:39 ` Pedro Alves
2018-05-22 14:39 ` 張俊芝
2018-05-22 15:17 ` Pedro Alves
2018-05-22 16:42 ` Pedro Alves
2018-05-22 17:31 ` 張俊芝 [this message]
2018-05-22 17:38 ` Pedro Alves
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=e4dfac0d-4177-c63c-1f28-a2707a489e3e@zjz.name \
--to=zjz@zjz.name \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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