Print this page
1209 fnmatch(3C) should mention FNM_IGNORECASE
Reviewed by: Marcel Telka <marcel@telka.sk>
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man3c/fnmatch.3c
+++ new/usr/src/man/man3c/fnmatch.3c
1 1 '\" te
2 2 .\" Copyright (c) 1992, X/Open Company Limited All Rights Reserved Portions Copyright (c) 2002, Sun Microsystems, Inc. All Rights Reserved
3 3 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at
4 4 .\" http://www.opengroup.org/bookstore/.
5 5 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
6 6 .\" This notice shall appear on any product containing this material.
7 7 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
8 8 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
9 9 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
10 -.TH FNMATCH 3C "Jul 24, 2002"
10 +.TH FNMATCH 3C "Jun 6, 2015"
11 11 .SH NAME
12 12 fnmatch \- match filename or path name
13 13 .SH SYNOPSIS
14 14 .LP
15 15 .nf
16 16 #include <fnmatch.h>
17 17
18 18 \fBint\fR \fBfnmatch\fR(\fBconst char *\fR\fIpattern\fR, \fBconst char *\fR\fIstring\fR, \fBint\fR \fIflags\fR);
19 19 .fi
20 20
21 21 .SH DESCRIPTION
22 22 .sp
23 23 .LP
24 24 The \fBfnmatch()\fR function matches patterns as described on the
25 25 \fBfnmatch\fR(5) manual page. It checks the \fIstring\fR argument to see if it
26 26 matches the \fIpattern\fR argument.
27 27 .sp
28 28 .LP
29 29 The \fIflags\fR argument modifies the interpretation of \fIpattern\fR and
30 30 \fIstring\fR. It is the bitwise inclusive \fBOR\fR of zero or more of the
31 31 following flags defined in the header <\fBfnmatch.h\fR>.
32 32 .sp
33 33 .ne 2
34 34 .na
35 35 \fB\fBFNM_PATHNAME\fR \fR
36 36 .ad
37 37 .RS 18n
38 38 If set, a slash (\fB/\fR) character in \fIstring\fR will be explicitly matched
|
↓ open down ↓ |
18 lines elided |
↑ open up ↑ |
39 39 by a slash in \fIpattern\fR; it will not be matched by either the asterisk
40 40 (\fB*\fR) or question-mark (\fB?\fR) special characters, nor by a bracket
41 41 (\fB[\|]\fR) expression.
42 42 .sp
43 43 If not set, the slash character is treated as an ordinary character.
44 44 .RE
45 45
46 46 .sp
47 47 .ne 2
48 48 .na
49 +\fB\fBFNM_IGNORECASE\fR\fR
50 +.ad
51 +.RS 18n
52 +If set, the \fIstring\fR will be transliterated to lower case before doing the
53 +actual match. This transliteration is done using \fBtowlower_l\fR(3C), using
54 +the locale of the current thread. If no locale is set, then the global locale
55 +is used instead.
56 +.sp
57 +If not set, the match will use \fIstring\fR with no changes, making the match
58 +case-sensitive.
59 +.RE
60 +
61 +.sp
62 +.ne 2
63 +.na
49 64 \fB\fBFNM_NOESCAPE\fR\fR
50 65 .ad
51 66 .RS 18n
52 67 If not set, a backslash character (\fB\e\fR) in \fIpattern\fR followed by any
53 68 other character will match that second character in \fIstring\fR. In
54 69 particular, "\fB\e\e\fR" will match a backslash in \fIstring\fR.
55 70 .sp
56 71 If set, a backslash character will be treated as an ordinary character.
57 72 .RE
58 73
59 74 .sp
60 75 .ne 2
61 76 .na
62 77 \fB\fBFNM_PERIOD\fR\fR
63 78 .ad
64 79 .RS 18n
65 80 If set, a leading period in \fIstring\fR will match a period in \fIpattern\fR;
66 81 where the location of "leading" is indicated by the value of
67 82 \fBFNM_PATHNAME\fR:
68 83 .RS +4
69 84 .TP
70 85 .ie t \(bu
71 86 .el o
72 87 If \fBFNM_PATHNAME\fR is set, a period is "leading" if it is the first
73 88 character in \fIstring\fR or if it immediately follows a slash.
74 89 .RE
|
↓ open down ↓ |
16 lines elided |
↑ open up ↑ |
75 90 .RS +4
76 91 .TP
77 92 .ie t \(bu
78 93 .el o
79 94 If \fBFNM_PATHNAME\fR is not set, a period is "leading" only if it is the first
80 95 character of \fIstring\fR.
81 96 .RE
82 97 .RE
83 98
84 99 .sp
85 -.LP
100 +.RS 18n
86 101 If not set, no special restrictions are placed on matching a period.
87 102 .SH RETURN VALUES
88 103 .sp
89 104 .LP
90 105 If \fIstring\fR matches the pattern specified by \fIpattern\fR, then
91 106 \fBfnmatch()\fR returns \fB0\fR. If there is no match, \fBfnmatch()\fR returns
92 107 \fBFNM_NOMATCH\fR, which is defined in the header <\fBfnmatch.h\fR>. If an
93 108 error occurs, \fBfnmatch()\fR returns another non-zero value.
94 109 .SH USAGE
95 110 .sp
96 111 .LP
97 112 The \fBfnmatch()\fR function has two major uses. It could be used by an
98 113 application or utility that needs to read a directory and apply a pattern
99 114 against each entry. The \fBfind\fR(1) utility is an example of this. It can
100 115 also be used by the \fBpax\fR(1) utility to process its \fIpattern\fR operands,
101 116 or by applications that need to match strings in a similar manner.
102 117 .sp
103 118 .LP
104 119 The name \fBfnmatch()\fR is intended to imply \fIfilename\fR match, rather than
105 120 \fIpathname\fR match. The default action of this function is to match
106 121 filenames, rather than path names, since it gives no special significance to
107 122 the slash character. With the \fBFNM_PATHNAME\fR flag, \fBfnmatch()\fR does
108 123 match path names, but without tilde expansion, parameter expansion, or special
109 124 treatment for period at the beginning of a filename.
110 125 .sp
111 126 .LP
112 127 The \fBfnmatch()\fR function can be used safely in multithreaded applications,
113 128 as long as \fBsetlocale\fR(3C) is not being called to change the locale.
114 129 .SH ATTRIBUTES
115 130 .sp
116 131 .LP
117 132 See \fBattributes\fR(5) for descriptions of the following attributes:
118 133 .sp
119 134
120 135 .sp
121 136 .TS
122 137 box;
123 138 c | c
124 139 l | l .
125 140 ATTRIBUTE TYPE ATTRIBUTE VALUE
126 141 _
127 142 CSI Enabled
128 143 _
129 144 Interface Stability Standard
130 145 _
131 146 MT-Level MT-Safe with exceptions
132 147 .TE
133 148
134 149 .SH SEE ALSO
135 150 .sp
136 151 .LP
137 152 \fBfind\fR(1), \fBpax\fR(1), \fBglob\fR(3C), \fBsetlocale\fR(3C),
138 153 \fBwordexp\fR(3C), \fBattributes\fR(5), \fBfnmatch\fR(5), \fBstandards\fR(5)
|
↓ open down ↓ |
43 lines elided |
↑ open up ↑ |
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX