[bug-gnulib] Re: bugs in regexp.c

[Sam Steingold]

> * Paul Eggert <address@hidden> [2005-03-08 17:03:27 -0800]:
>
> Sam Steingold <address@hidden> writes:
>
>> regexp.c exhibits the following 8 bugs:
>>
>> 1. regcomp("*a"): "Invalid preceding regular expression"
>> 2. regcomp("^*"): "Invalid preceding regular expression"
>> 3. regcomp("$*"): "Invalid preceding regular expression"
>> 4. regcomp("(*)b"): "Invalid preceding regular expression"
>> 5. regcomp("{[^}\n]*}"): "Invalid content of \\{\\}"
>> 6. regcomp("{[^}\n]*}"): "Invalid content of \\{\\}"
>> 7. regcomp ("{[^}\n]*}"): "Invalid content of \\{\\}"
>> 8. regcomp("[[:xdigit]+") works, but when the result is matched against
>>    "0[x:dig", it matches just "[", not "[x:dig"
>
> (3) is a bug, but the others aren't bugs, surely, since POSIX says
> those other EREs are invalid or have undefined behavior.

what's wrong with 8?


> Perhaps you need to update the CLISP regexp test suite?

maybe.

> From the current gnulib code, I don't see how (3) could happen, so I'm
> at a bit of a loss about how that bug occurs.

well, it _does_ occur.

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.memri.org/> <http://www.honestreporting.com> <http://pmw.org.il/>
<http://www.iris.org.il> <http://www.camera.org> <http://www.mideasttruth.com/>
If You Want Breakfast In Bed, Sleep In the Kitchen.