From: Mike Frysinger <vapier@gentoo.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: use character classes rather than ranges
Date: Mon, 19 Mar 2012 15:07:00 -0000 [thread overview]
Message-ID: <201203191107.07237.vapier@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1203191148440.9545@digraph.polyomino.org.uk>
[-- Attachment #1: Type: Text/Plain, Size: 1227 bytes --]
On Monday 19 March 2012 07:52:08 Joseph S. Myers wrote:
> On Mon, 19 Mar 2012, Mike Frysinger wrote:
> > A-Z ranges don't work in all locales, so use character classes instead.
>
> Are these patterns really meant to depend on the user's locale (and
> support locale-specific letters) or are they related to the checked-in
> source code (in which case they should support just ASCII letters and
> digits - either the relevant program should be run in the C locale, or as
> in GCC's option-handling awk scripts the full sets of letters and digits
> should be given explicitly somewhere)?
>
> (Using character classes like you do is fine - *if* either the user's
> locale is correct for this code or the programs explicitly run in the C
> locale.)
some are meant for processing source files which get checked in while others
are processing user flags. the gennltvals.sh script could be made to work by
forcing a C locale, but the configure script would be tricky.
these changes might over match input if the processed source is wrong, but for
all correct inputs, these groups should give the same output regardless of
locale which is why i didn't try going the mess-with-active-locale route.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-19 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 4:54 Mike Frysinger
2012-03-19 11:52 ` Joseph S. Myers
2012-03-19 15:07 ` Mike Frysinger [this message]
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=201203191107.07237.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.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