|?||Matches any single character (including a single UTF-8 multibyte character, so ? can match more than one byte).|
|*||Matches any sequence of zero or more characters.|
|\||Turns off any special meaning of the following character; the following character will match itself in the text. \ will escape any character, including another backslash or a comma that otherwise would separate a pattern from the next pattern in an expression. Note that \ is not special inside a character range (no metacharacters are).|
A character set, which matches any single character that falls within that
set. The presence of a character between the brackets adds that character
to the set; for example, [amv] specifies the set containing the
characters a, m, and v. A range of characters may be specified
using -; for example, [0-5abc] is equivalent to [012345abc]. The
order of characters is as defined in the UTF-8 character set, and if the
start character of such a range falls after the ending character of the
range in that ranking the results of attempting a match with that pattern
In order to include a literal ] character in the set, it must be the first character of the set (possibly following ^); for example, a] matches either ] or a. To include a literal - character in the set, it must be either the first or the last character of the set. Backslashes have no special meaning inside a character set, nor do any other of the wildmat metacharacters.
|[^...]||A negated character set. Follows the same rules as a character set above, but matches any character not contained in the set. So, for example, [^]-] matches any character except ] and -.|
When matching a wildmat expression against some text, each comma-separated pattern is matched in order from left to right. In order to match, the pattern must match the whole text; in regular expression terminology, its implicitly anchored at both the beginning and the end. For example, the pattern a matches only the text a; it doesnt match ab or ba or even aa. If none of the patterns match, the whole expression doesnt match. Otherwise, whether the expression matches is determined entirely by the rightmost matching pattern; the expression matches the text if and only if the rightmost matching pattern is not negated.
For example, consider the text news.misc. The expression * matches this text, of course, as does comp.*,news.* (because the second pattern matches). news.*,!news.misc does not match this text because both patterns match, meaning that the rightmost takes precedence, and the rightmost matching pattern is negated. news.*,!news.misc,*.misc does match this text, since the rightmost matching pattern is not negated.
Note that the expression !news.misc cant match anything. Either the pattern doesnt match, in which case no patterns match and the expression doesnt match, or the pattern does match, in which case because its negated the expression doesnt match. *,!news.misc, on the other hand, is a useful pattern that matches anything except news.misc.
! has significance only as the first character of a pattern; anywhere else in the pattern, it matches a literal ! in the text like any other non-metacharacter.
If the uwildmat_poison interface is used, then @ behaves the same as ! except that if an expression fails to match because the rightmost matching pattern began with @, UWILDMAT_POISON is returned instead of UWILDMAT_FAIL.
If the uwildmat_simple interface is used, the matching rules are the same as above except that none of !, @, or , have any special meaning at all and only match those literal characters.
All of these functions internally convert the passed arguments to const unsigned char pointers. The only reason why they take regular char pointers instead of unsigned char is for the convenience of INN and other callers that may not be using unsigned char everywhere they should. In a future revision, the public interface should be changed to just take unsigned char pointers.
Written by Rich $alz <email@example.com> in 1986, and posted to Usenet several times since then, most notably in comp.sources.misc in March, 1991.
Lars Mathiesen <firstname.lastname@example.org> enhanced the multi-asterisk failure mode in early 1991.
Rich and Lars increased the efficiency of star patterns and reposted it to comp.sources.misc in April, 1991.
Robert Elz <email@example.com> added minus sign and close bracket handling in June, 1991.
Russ Allbery <firstname.lastname@example.org> added support for comma-separated patterns and the ! and @ metacharacters to the core wildmat routines in July, 2000. He also added support for UTF-8 characters, changed the default behavior to assume that both the text and the pattern are in UTF-8, and largely rewrote this documentation to expand and clarify the description of how a wildmat expression matches.
Please note that the interfaces to these functions are named uwildmat and the like rather than wildmat to distinguish them from the wildmat function provided by Rich $alzs original implementation. While this code is heavily based on Richs original code, it has substantial differences, including the extension to support UTF-8 characters, and has noticable functionality changes. Any bugs present in it arent Richs fault.
$Id: uwildmat.pod 9767 2014-12-07 21:13:43Z iulius $
grep(1), fnmatch(3), regex(3), regexp(3).
|INN 2.6.0||UWILDMAT (3)||2015-09-12|