GNU bug report logs - #5970
regex won't do lazy matching

Previous Next

Package: coreutils;

Reported by: a g <mewalig <at> gmail.com>

Date: Mon, 19 Apr 2010 02:02:01 UTC

Severity: normal

Done: Bob Proulx <bob <at> proulx.com>

Bug is archived. No further changes may be made.

Full log


Message #34 received at 5970 <at> debbugs.gnu.org (full text, mbox):

From: Linda Walsh <coreutils <at> tlinx.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: a g <mewalig <at> gmail.com>, 5970 <at> debbugs.gnu.org
Subject: Re: bug#5970: regex won't do lazy matching
Date: Sun, 02 May 2010 23:21:17 -0700

Andreas Schwab wrote:
> a g <mewalig <at> gmail.com> writes:
> 
>>   regex_test "a[^x]*?a" "a1a2a"
> 
> <http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_04_06>:
> 
>  9.4.6 EREs Matching Multiple Characters
>    [...]
>    The behavior of multiple adjacent duplication symbols ('+', '*', '?',
>    and intervals) produces undefined results.
> 
> Andreas.
---

Sorry, late to conversation, but reading email.

There was a time in QA that "undefined results" and bug was synonymous.

That a spec would say that is lame.

Personally, I think if it isn't compatible with the Perl Regex, it's
a bug, but that's purely informed personal bias.  :-)

-l




This bug report was last modified 15 years and 24 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.