Re: Equivalence classes handled differently in mb vs non-mb patterns

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Equivalence classes handled differently in mb vs non-mb patterns
Date	2020-07-30 15:51 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.331.1596138749.2739.bug-bash@gnu.org> (permalink)
References	<e988ae23-36bf-43c2-8c4c-a9abad806ce8@gigawatt.nl> <7301014c-b5a8-5b79-14a1-cef88af8aef7@case.edu>

Show all headers | View raw

On 7/28/20 4:17 AM, Harald van Dijk wrote:

> Bash Version: 5.0
> Patch Level: 18
> Release Status: release
> 
> Description:
>     In lib/glob/smatch.c, there are two functions that are used to
>     check equivalence classes in patterns: collequiv, and
>         collequiv_wc. The former is used if the pattern does not contain
>         any multi-byte characters, the latter otherwise, With
>         exceptions that are not relevant to this bug. The two functions
>         do not give the same results: collequiv does not implement the
>         fnmatch() fallback code that collequiv_wc does implement,
>         leading to inconsistent matching for ASCII-only equivalence
>         classes.

Thanks for the report, and the prodding to do the work that has been
pending in this area.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Equivalence classes handled differently in mb vs non-mb patterns Chet Ramey <chet.ramey@case.edu> - 2020-07-30 15:51 -0400

csiph-web