Kurt Roeckx <[EMAIL PROTECTED]> wrote:
>
>> Not quite. In the context of case patterns and fnmatch, quote removal
>> is not performed.
>
> You mean fnmatch() gets called with the FNM_NOESCAPE flag?
No. I mean that on the input path to fnmatch(), the escape characters
have to be there.
--
Debia
Kurt Roeckx <[EMAIL PROTECTED]> wrote:
>
>> Not quite. In the context of case patterns and fnmatch, quote removal
>> is not performed.
>
> You mean fnmatch() gets called with the FNM_NOESCAPE flag?
No. I mean that on the input path to fnmatch(), the escape characters
have to be there.
--
Debia
On Sat, Apr 17, 2004 at 10:44:27PM +0200, Kurt Roeckx wrote:
>
> If I understand Herbert Xu correctly, he's saying the regex
> should be written as:
> *[][~#$^&*(){}\|;<>?]*
No, the way it's written currently is fine.
It's glibc's fnmatch(3) implementation that's broken.
Cheers,
--
Debian GNU/
On Sat, Apr 17, 2004 at 10:44:27PM +0200, Kurt Roeckx wrote:
>
> If I understand Herbert Xu correctly, he's saying the regex
> should be written as:
> *[][~#$^&*(){}\|;<>?]*
No, the way it's written currently is fine.
It's glibc's fnmatch(3) implementation that's broken.
Cheers,
--
Debian GNU/
On Sat, Apr 17, 2004 at 12:14:39PM -0700, Ben Pfaff wrote:
> Herbert Xu <[EMAIL PROTECTED]> writes:
>
> >> Accordingly, I believe that the pattern in your example means
> >> "backslash, followed by a, followed by closing square bracket", not what
> >> you think it means.
> >
> > You're quite right
Herbert Xu <[EMAIL PROTECTED]> writes:
>> Accordingly, I believe that the pattern in your example means
>> "backslash, followed by a, followed by closing square bracket", not what
>> you think it means.
>
> You're quite right. This is reaffirmed by the POSIX document for
> basic regular expressio
On Sat, Apr 17, 2004 at 12:14:39PM -0700, Ben Pfaff wrote:
> Herbert Xu <[EMAIL PROTECTED]> writes:
>
> >> Accordingly, I believe that the pattern in your example means
> >> "backslash, followed by a, followed by closing square bracket", not what
> >> you think it means.
> >
> > You're quite right
Herbert Xu <[EMAIL PROTECTED]> writes:
>> Accordingly, I believe that the pattern in your example means
>> "backslash, followed by a, followed by closing square bracket", not what
>> you think it means.
>
> You're quite right. This is reaffirmed by the POSIX document for
> basic regular expressio
On Sat, Apr 17, 2004 at 07:58:21AM +1000, Herbert Xu wrote:
> On Fri, Apr 16, 2004 at 08:49:14PM +0200, Kurt Roeckx wrote:
> >
> > After reading all that you have to get confused about what "[\[\]\\]" means.
> > At the "highest level" it says that the '\' should be discarded,
>
> Not quite. In th
On Fri, Apr 16, 2004 at 08:49:14PM +0200, Kurt Roeckx wrote:
>
> After reading all that you have to get confused about what "[\[\]\\]" means.
> At the "highest level" it says that the '\' should be discarded,
Not quite. In the context of case patterns and fnmatch, quote removal
is not performed.
On Sat, Apr 17, 2004 at 07:58:21AM +1000, Herbert Xu wrote:
> On Fri, Apr 16, 2004 at 08:49:14PM +0200, Kurt Roeckx wrote:
> >
> > After reading all that you have to get confused about what "[\[\]\\]" means.
> > At the "highest level" it says that the '\' should be discarded,
>
> Not quite. In th
On Fri, Apr 16, 2004 at 08:49:14PM +0200, Kurt Roeckx wrote:
>
> After reading all that you have to get confused about what "[\[\]\\]" means.
> At the "highest level" it says that the '\' should be discarded,
Not quite. In the context of case patterns and fnmatch, quote removal
is not performed.
12 matches
Mail list logo
