From: Carlos O'Donell <carlos@redhat.com>
To: Andreas Schwab <schwab@suse.de>, Florian Weimer <fweimer@redhat.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
GNU C Library <libc-alpha@sourceware.org>,
Rich Felker <dalias@aerifal.cx>, Mike Fabian <mfabian@redhat.com>,
Zorro Lang <zlang@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [PATCH] Keep expected behaviour for [a-z] and [A-z] (Bug 23393).
Date: Thu, 26 Jul 2018 13:25:00 -0000 [thread overview]
Message-ID: <6e16e657-d946-53ce-2010-daaa523cec1f@redhat.com> (raw)
In-Reply-To: <mvmh8kmxve1.fsf@suse.de>
On 07/26/2018 04:18 AM, Andreas Schwab wrote:
> On Jul 26 2018, Florian Weimer <fweimer@redhat.com> wrote:
>
>> The bash implementation of glob always uses strcoll/wcscoll ordering when
>> globasciirange is not active. It does not use collation element ordering,
>> so rearranging collation data does not affect it.
>
> Why does strcoll not agree with the collation sequence?
There are two terms that mean very different things.
The strcoll output and collation sequence are the same.
The collation sequence is not the same as the collation element ordering
(the order of the rules in the source file).
POSIX mandated the use of collation element ordering (not sequence) for
regular expression ranges, and then decided this was a bad idea and instead
made it unspecified.
In glibc we continue to implement and support collation element ordering,
not collation sequence, for posix regular expression ranges.
Even collation sequence is a bad idea because [a-z] does not include all the
z's that are sorted after z, and you need special collation element markers
like AFTER-Z to find all the z's. Instead we should use rational ranges
and make everything based on code points to make it portable across all
locales.
Cheers,
Carlos.
prev parent reply other threads:[~2018-07-26 13:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 19:43 Carlos O'Donell
2018-07-19 20:39 ` Florian Weimer
2018-07-20 18:49 ` Carlos O'Donell
2018-07-20 19:02 ` Rich Felker
2018-07-20 19:19 ` Florian Weimer
2018-07-20 21:56 ` Carlos O'Donell
2018-07-23 15:11 ` Florian Weimer
2018-07-23 18:09 ` Rational Ranges - Rafal and Mike's opinion? " Carlos O'Donell
2018-07-24 20:45 ` Rafal Luzynski
2018-07-24 20:53 ` Carlos O'Donell
2018-07-24 20:59 ` Carlos O'Donell
2018-07-25 15:44 ` Mike FABIAN
2018-07-25 15:54 ` [PATCHv3] Expected behaviour for a-z, A-Z, and 0-9 " Carlos O'Donell
2018-07-25 20:19 ` Florian Weimer
2018-07-25 20:25 ` Carlos O'Donell
2018-07-25 20:31 ` Florian Weimer
2018-07-25 20:57 ` [PATCHv4] " Carlos O'Donell
2018-07-26 2:34 ` [PATCHv4a] " Carlos O'Donell
2018-07-26 14:51 ` Florian Weimer
2018-07-26 14:59 ` Carlos O'Donell
2018-07-28 1:12 ` [WIPv5] " Carlos O'Donell
2018-07-30 17:40 ` Florian Weimer
2018-07-30 17:45 ` Carlos O'Donell
2018-07-30 17:54 ` Florian Weimer
2018-07-30 18:26 ` Carlos O'Donell
2018-07-30 18:34 ` Florian Weimer
2018-07-31 2:18 ` Carlos O'Donell
2018-07-25 21:06 ` [PATCHv3] " Rafal Luzynski
2018-07-25 21:12 ` Carlos O'Donell
2018-07-25 21:35 ` [PATCH] Keep expected behaviour for [a-z] and [A-z] " Carlos O'Donell
2018-07-25 22:50 ` Florian Weimer
2018-07-26 1:20 ` Carlos O'Donell
2018-07-26 8:09 ` Andreas Schwab
2018-07-26 9:16 ` Florian Weimer
2018-07-26 1:33 ` Jonathan Nieder
2018-07-26 1:49 ` Carlos O'Donell
2018-07-26 2:16 ` Jonathan Nieder
2018-07-26 3:48 ` Carlos O'Donell
2018-07-26 7:42 ` Florian Weimer
2018-07-26 8:18 ` Andreas Schwab
2018-07-26 9:15 ` Florian Weimer
2018-07-26 13:25 ` Carlos O'Donell [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=6e16e657-d946-53ce-2010-daaa523cec1f@redhat.com \
--to=carlos@redhat.com \
--cc=dalias@aerifal.cx \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=jrnieder@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=mfabian@redhat.com \
--cc=schwab@suse.de \
--cc=zlang@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).