DO NOT REPLY [Bug 45461] GlobCompiler: * should not match the path separator '/'
[email protected] Tue, 22 Jul 2008 12:39:49 -0700 (PDT)
| Newsgroups | gmane.comp.jakarta.oro.devel |
|---|---|
| Message-ID | <[email protected]> |
https://issues.apache.org/bugzilla/show_bug.cgi?id=45461 Daniel F. Savarese <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Daniel F. Savarese <[email protected]> 2008-07-22 12:39:48 PST --- This is not a bug and is the intended behavior. GlobCompiler is not meant to be an implementation of glob(3). The API docs explain the intended behavior (http://jakarta.apache.org/oro/api/org/apache/oro/text/GlobCompiler.html): * - Matches zero or more instances of any character. If the STAR_CANNOT_MATCH_NULL_MASK option is used, * matches one or more instances of any character. glob(3) concerns itself with matching file system path names within the context of shell filename expansion. Many applications use glob-style expressions outside of the file system path name context and expect * to match any character. Even a file system-oriented program such as find (at least the GNU implementation) does not conform to glob(3)/glob(7). For example, find -path "*" will match all intervening slashes. If you intend to use GlobCompiler and require the ability to not match slashes, we can add a STAR_CANNOT_MATCH_SLASH_MASK option. However, it would be more efficient to discuss this on the mailing list. In general, it is more effective to raise and discuss questions on the mailing list first and open issues only after it's been confirmed that there is indeed an issue that requires opening. If it is agreed that STAR_CANNOT_MATCH_SLASH_MASK is the way to go, then an improvement/new feature issue can be opened. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.