NAME<\/a> File::FnMatch \u2212 simple filename and pathname matching<\/p>\n use File::FnMatch qw(:fnmatch); # import everything File::FnMatch::fnmatch()<\/b> provides simple, shell-like pattern matching.<\/p>\n Though considerably less powerful than regular expressions, shell patterns are nonetheless useful and familiar to a large audience of end-users.<\/p>\n Functions<\/b> Returns true if PATTERN<\/small><\/i> matches STRING<\/small><\/i> , undef otherwise. FLAGS<\/small><\/i> may be the bitwise OR<\/small> \u2019ing of any supported FNM_* constants (see below).<\/p>\n Constants<\/b> Do not treat a backslash (\u2019\u2019) in PATTERN<\/small><\/i> specially. Otherwise, a backslash escapes the following character.<\/p>\n FNM_PATHNAME<\/small><\/p>\n Prohibit wildcards from matching a slash (\u2019\/\u2019).<\/p>\n FNM_PERIOD<\/small><\/p>\n Prohibit wildcards from matching a period (\u2019.\u2019) at the start of a string and, if FNM_PATHNAME<\/small> is also given, immediately after a slash.<\/p>\n Other possibilities include at least FNM_CASEFOLD<\/small> (compare “qr\/\/i”), FNM_LEADING_DIR<\/small> to restrict matching to everything before the first \u2019\/\u2019, FNM_FILE_NAME<\/small> as a synonym for FNM_PATHNAME,<\/small> and the rather more exotic FNM_EXTMATCH.<\/small> Consult your system documentation for details.<\/p>\n EXPORT<\/small><\/b> Wildcards are the question mark (\u2019?\u2019) to match any single character and the asterisk (\u2019*\u2019) to match zero or more characters. FNM_PATHNAME<\/small> and FNM_PERIOD<\/small> restrict the scope of the wildcards, notably supporting the UNIX<\/small> convention of concealing “dotfiles”:<\/p>\n Bracket expressions, enclosed by \u2019[\u2019 and \u2019]\u2019, match any of a set of characters specified explicitly (“[abcdef]”), as a range (“[a\u2212f0\u22129]”), or as the combination these (“[a\u2212f0\u22129XYZ]”). Additionally, many implementations support named character classes such as “[[:xdigit:]]”. Character sets may be negated with an initial \u2019!\u2019 (“[![:space:]]”).<\/p>\n Locale influences the meaning of fnmatch()<\/b> patterns.<\/p>\n Most UNIX-like systems provide an fnmatch implementation. This module will not work on platforms lacking an implementation, most notably Win32.<\/p>\n File::Glob, POSIX::setlocale, fnmatch<\/b>(3)<\/p>\n Michael J. Pomraning<\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
PATTERN SYNTAX<\/a>
CAVEATS<\/a>
SEE ALSO<\/a>
AUTHOR<\/a>
COPYRIGHT AND LICENSE<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
# shell\u2212style: match “\/a\/bc”, but not “\/a\/.bc” nor “\/a\/b\/c”
fnmatch(“\/a\/*”, $fn, FNM_PATHNAME|FNM_PERIOD);
# find our A\u2212 executables only
grep { fnmatch(“A\u2212*.exe”, $_) } readdir SOMEDIR;<\/p>\nDESCRIPTION <\/a> <\/h2>\n
fnmatch ( PATTERN, STRING<\/small> [, FLAGS<\/small> ] )<\/p>\n
FNM_NOESCAPE<\/small><\/p>\n
None by default. The export tag “:fnmatch” exports the fnmatch function and all available FNM_* constants.<\/p>\nPATTERN SYNTAX <\/a> <\/h2>\n
CAVEATS <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
AUTHOR <\/a> <\/h2>\n