On 9/3/07, Martin Simmons <[EMAIL PROTECTED]> wrote: > Mon, 3 Sep 2007 21:29:24 +0200, Kern Sibbald said: .... > > To the best of my knowledge the following are not wildcard matches. If they > > are can you point me to the definition of [:alpha:]? > > > > > [36] *[[:alpha:]]/*[[:alnum:]] does not match a/b -> FAIL > > > [37] *[![:digit:]]*/[![:d-d] does not match a/b -> FAIL > > > [38] *[![:digit:]]*/[[:d-d] does not match a/[ -> FAIL > > > > > > > I think they have a broken test set -- someone confused wildcards and > > regular > > expressions, or defined the test results backwards. > > > > >From every definition I can find, wildcards included in fnmatch, contain > > >only > > > > * > > ? > > [set] > > [!set] > > > > anything else is an extension that is not in basic shell wildcards or > > something from regular expressions. You need to be careful because a lot of > > documents refer to regular expressions as wildcards, but as you know, they > > are not at all the same thing. > > The [:class:] might come from POSIX. It is certainly allowed by this spec:
Yeah, those are POSIX character classes which are supported by most modern regular expression engines, especially ones in the "Perl Compatible" class. Whether they should or shouldn't affect globbing is a different question. It would appear that http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_13_03 says that they should affect globbing. Of course the windows file globbing API /doesnt/ recognize them, but then again it doesn't recognize many of the globbing patterns. :-) Yves -- perl -Mre=debug -e "/just|another|perl|hacker/" ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
