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


Groups > gnu.bash.bug > #15382

Re: Incorrect example for `[[` command.

From Ilkka Virta <itvirta@iki.fi>
Newsgroups gnu.bash.bug
Subject Re: Incorrect example for `[[` command.
Date 2019-09-20 16:30 +0300
Message-ID <mailman.606.1568986234.2190.bug-bash@gnu.org> (permalink)
References <CAD0rTC7W20s7-8np7Z+CmZQczTQ+LX=Y1x01gAenewrpiJS5jw@mail.gmail.com> <20190920124827.GP28751@eeg.ccf.org> <70f5667e-d91e-a4cf-fef0-b72c7d61a29a@iki.fi>

Show all headers | View raw


On 20.9. 15:48, Greg Wooledge wrote:
> but after the regex-glob-thing, it says:
> 
>    That means values like ‘aab’ and ‘ aaaaaab’ will match
> 
> So there's a shift in intent between a? and a+ in what's supposed to be
> a regular expression.  Although of course the sentence is *literally*
> true because the regex would be unanchored, and therefore it's sufficient
> to match only the 'ab', and the rest of the input doesn't matter.
> But that's just confusing, and doesn't belong in this kind of document.

It goes on to say "as will a line containing a 'b' anywhere in its 
value", so the text does recognize the zero-width-matching parts don't 
affect what matches. (I suppose they would affect what goes to 
BASH_REMATCH[0], but the text doesn't mention that.)

I think it would be a better example with the anchored version also 
presented for comparison.

-- 
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-20 16:30 +0300

csiph-web