summaryrefslogtreecommitdiffstats
path: root/libiberty/fnmatch.txh
diff options
context:
space:
mode:
authordj <dj@138bc75d-0d04-0410-961f-82ee72b054a4>2001-10-16 02:50:13 +0000
committerdj <dj@138bc75d-0d04-0410-961f-82ee72b054a4>2001-10-16 02:50:13 +0000
commit349e82761f2e7e2100e6154bed1f2125cb01be3a (patch)
tree58903ff3e4335306b7c9f5c24e8baf3b9a9922a8 /libiberty/fnmatch.txh
parentfddea9c57af89ec3402bce5c65c755b682521fb0 (diff)
downloadppe42-gcc-349e82761f2e7e2100e6154bed1f2125cb01be3a.tar.gz
ppe42-gcc-349e82761f2e7e2100e6154bed1f2125cb01be3a.zip
* Makefile.in (TEXIFILES): Add fnmatch.txh.
(maint-undoc): New. maint-tool: Add "undoc" tool. * alloca.c, argv.c, asprintf.c, choose-temp.c, concat.c, fdmatch.c, ffs.c, getruntime.c, insque.c, lbasename.c, make-temp-file.c, mkstemps.c, pexecute.c, random.c, spaces.c, strerror.s, strsignal.c, strtol.c, vasprintf.c: Add or update documentation. * fnmatch.txh: New. * functions.texi: Regenerate. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@46274 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'libiberty/fnmatch.txh')
-rw-r--r--libiberty/fnmatch.txh48
1 files changed, 48 insertions, 0 deletions
diff --git a/libiberty/fnmatch.txh b/libiberty/fnmatch.txh
new file mode 100644
index 00000000000..dfdac2406aa
--- /dev/null
+++ b/libiberty/fnmatch.txh
@@ -0,0 +1,48 @@
+@deftypefn Replacement int fnmatch (const char *@var{pattern}, const char *@var{string}, int @var{flags})
+
+Matches @var{string} against @var{pattern}, returning zero if it
+matches, @code{FNM_NOMATCH} if not. @var{pattern} may contain the
+wildcards @code{?} to match any one character, @code{*} to match any
+zero or more characters, or a set of alternate characters in square
+brackets, like @samp{[a-gt8]}, which match one character (@code{a}
+through @code{g}, or @code{t}, or @code{8}, in this example) if that one
+character is in the set. A set may be inverted (i.e. match anything
+except what's in the set) by giving @code{^} or @code{!} as the first
+character in the set. To include those characters in the set, list them
+as anything other than the first character of the set. To include a
+dash in the set, list it last in the set. A backslash character makes
+the following character not special, so for example you could match
+against a literal asterisk with @samp{\*}. To match a literal
+backslash, use @samp{\\}.
+
+@code{flags} controls various aspects of the matching process, and is a
+boolean OR of zero or more of the following values (defined in
+@code{<fnmatch.h>}:
+
+@table @code
+
+@item FNM_PATHNAME
+@itemx FNM_FILE_NAME
+@var{string} is assumed to be a path name. No wildcard will ever match
+@code{/}.
+
+@item FNM_NOESCAPE
+Do not interpret backslashes as quoting the following special character.
+
+@item FNM_PERIOD
+A leading period (at the beginning of @var{string}, or if
+@code{FNM_PATHNAME} after a slash) is not matched by @code{*} or
+@code{?} but must be matched explicitly.
+
+@item FNM_LEADING_DIR
+Means that @var{string} also matches @var{pattern} if some initial part
+of @var{string} matches, and is followed by @code{/} and zero or more
+characters. For example, @samp{foo*} would match either @samp{foobar}
+or @samp{foobar/grill}.
+
+@item FNM_CASEFOLD
+Ignores case when performing the comparison.
+
+@end table
+
+@end deftypefn
OpenPOWER on IntegriCloud