Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14556 > unrolled thread

Re: built-in regex matches wrong character

Started byChet Ramey <chet.ramey@case.edu>
First post2018-09-06 10:25 -0400
Last post2018-09-06 10:25 -0400
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: built-in regex matches wrong character Chet Ramey <chet.ramey@case.edu> - 2018-09-06 10:25 -0400

#14556 — Re: built-in regex matches wrong character

FromChet Ramey <chet.ramey@case.edu>
Date2018-09-06 10:25 -0400
SubjectRe: built-in regex matches wrong character
Message-ID<mailman.446.1536243929.1284.bug-bash@gnu.org>
On 9/6/18 10:23 AM, Eric Blake wrote:

> But bash could be taught to convert any regex that contains a range with
> both endpoints ASCII into a different bracket expression before handing
> things over to regcomp().  That is, if the user is matching against [a-d],
> bash hands [abcd] to regcomp() instead.  You don't need a flag in regcomp()
> to get RRI, just merely some pre-processing (and often memory allocation,
> as the expansion of a range into a non-range tends to require more
> characters).

Someone would have to write that code.

-- 
``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/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web