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


Groups > gnu.bash.bug > #15388

Re: Incorrect example for `[[` command.

From Ilkka Virta <itvirta@iki.fi>
Newsgroups gnu.bash.bug
Subject Re: Incorrect example for `[[` command.
Date 2019-09-21 12:34 +0300
Message-ID <mailman.713.1569058490.2190.bug-bash@gnu.org> (permalink)
References <CAD0rTC7W20s7-8np7Z+CmZQczTQ+LX=Y1x01gAenewrpiJS5jw@mail.gmail.com> <8e7c8ea4-2fdf-4809-0b50-ea1bfbbec165@case.edu> <CAD0rTC68qoXvCV9SLP1dJ8Gvg71W7bg9yt8jjpmpESK-jKD7Wg@mail.gmail.com> <bf5a1810-8316-239c-0c5a-f85803048ab6@iki.fi>

Show all headers | View raw


On 21.9. 03:12, hk wrote:
> Thanks for the reply. I was wrong in my report. It does match values like
> aab and  aaaaaab  in its original form.

In some systems, yes. (It does that on my Debian, but doesn't work at 
all on my Mac.)

> It is syntatically correct as a regular expression. 

[[:space:]]*?(a)b  isn't a well-defined POSIX ERE:

   9.4.6 EREs Matching Multiple Characters

   The behavior of multiple adjacent duplication symbols ( '+', '*', '?',
   and intervals) produces undefined results.

https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/basedefs/V1_chap09.html


-- 
Ilkka Virta / itvirta@iki.fi

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


Thread

Re: Incorrect example for `[[` command. Ilkka Virta <itvirta@iki.fi> - 2019-09-21 12:34 +0300

csiph-web