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


Groups > gnu.bash.bug > #14314

Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~

From Chet Ramey <chet.ramey@case.edu>
Newsgroups gnu.bash.bug
Subject Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~
Date 2018-07-10 10:50 -0400
Message-ID <mailman.3376.1531234202.1292.bug-bash@gnu.org> (permalink)
References <5b440fe8.1c69fb81.948f6.4d1e@mx.google.com> <20180710122718.wrrzjuqpmpns4o4o@eeg.ccf.org> <20180710130234.r5mwjc62adids7m5@monk>

Show all headers | View raw


On 7/10/18 9:02 AM, Paulo Marcel Coelho Aragão wrote:
> On Tue, Jul 10, 2018 at 08:27:18AM -0400, Greg Wooledge wrote:
>> Bash uses ERE (Extended Regular Expressions) here.  There is no \< or \>
>> in an ERE.
>>
>> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_04
> 
> Thanks for the reference. The document lists only ^ and $ as anchors. However, this indicates to me that bash recognizes \< \> as word anchors:

No, it doesn't. It indicates that the system's POSIX regular expression
implementation has extensions.

> Empirically all this demonstrates:
> 
> 1. bash recognizes \< \> \b as word anchors

No, it doesn't.

> 2. bash doesn't evaluate them correctly when used as literals

Yes, it does. It may not conform to your assumptions.

> 3. bash evaluates them correctly when used with parameter expansion

No. It passes them to the system's POSIX regexp library function, which
understands them as an extension.


-- 
``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 | Unroll thread


Thread

Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Chet Ramey <chet.ramey@case.edu> - 2018-07-10 10:50 -0400

csiph-web