1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
|
'\" t
.\" Copyright (C) 2006 Justin Pryzby <pryzbyj@justinpryzby.com>
.\"
.\" %%%LICENSE_START(PERMISSIVE_MISC)
.\" Permission is hereby granted, free of charge, to any person obtaining
.\" a copy of this software and associated documentation files (the
.\" "Software"), to deal in the Software without restriction, including
.\" without limitation the rights to use, copy, modify, merge, publish,
.\" distribute, sublicense, and/or sell copies of the Software, and to
.\" permit persons to whom the Software is furnished to do so, subject to
.\" the following conditions:
.\"
.\" The above copyright notice and this permission notice shall be
.\" included in all copies or substantial portions of the Software.
.\"
.\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
.\" EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
.\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
.\" IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
.\" CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
.\" TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
.\" SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
.\" %%%LICENSE_END
.\"
.\" References:
.\" glibc manual and source
.\"
.\" 2006-05-19, mtk, various edits and example program
.\"
.TH rpmatch 3 2023-02-05 "Linux man-pages 6.03"
.SH NAME
rpmatch \- determine if the answer to a question is affirmative or negative
.SH LIBRARY
Standard C library
.RI ( libc ", " \-lc )
.SH SYNOPSIS
.nf
.B #include <stdlib.h>
.PP
.BI "int rpmatch(const char *" response );
.fi
.PP
.RS -4
Feature Test Macro Requirements for glibc (see
.BR feature_test_macros (7)):
.RE
.PP
.BR rpmatch ():
.nf
Since glibc 2.19:
_DEFAULT_SOURCE
glibc 2.19 and earlier:
_SVID_SOURCE
.fi
.SH DESCRIPTION
.BR rpmatch ()
handles a user response to yes or no questions, with
support for internationalization.
.PP
.I response
should be a null-terminated string containing a
user-supplied response, perhaps obtained with
.BR fgets (3)
or
.BR getline (3).
.PP
The user's language preference is taken into account per the
environment variables
.BR LANG ,
.BR LC_MESSAGES ,
and
.BR LC_ALL ,
if the program has called
.BR setlocale (3)
to effect their changes.
.PP
Regardless of the locale, responses matching
.B \[ha][Yy]
are always accepted as affirmative, and those matching
.B \[ha][Nn]
are always accepted as negative.
.SH RETURN VALUE
After examining
.IR response ,
.BR rpmatch ()
returns 0 for a recognized negative response ("no"), 1
for a recognized positive response ("yes"), and \-1 when the value
of
.I response
is unrecognized.
.SH ERRORS
A return value of \-1 may indicate either an invalid input, or some
other error.
It is incorrect to only test if the return value is nonzero.
.PP
.BR rpmatch ()
can fail for any of the reasons that
.BR regcomp (3)
or
.BR regexec (3)
can fail; the cause of the error
is not available from
.I errno
or anywhere else, but indicates a
failure of the regex engine (but this case is indistinguishable from
that of an unrecognized value of
.IR response ).
.SH ATTRIBUTES
For an explanation of the terms used in this section, see
.BR attributes (7).
.ad l
.nh
.TS
allbox;
lbx lb lb
l l l.
Interface Attribute Value
T{
.BR rpmatch ()
T} Thread safety MT-Safe locale
.TE
.hy
.ad
.sp 1
.SH STANDARDS
.BR rpmatch ()
is not required by any standard,
but available under the GNU C library, FreeBSD, and AIX.
.SH BUGS
The
.BR YESEXPR " and " NOEXPR
of some locales (including "C") only inspect the first character of the
.IR response .
This can mean that "yno" et al. resolve to
.BR 1 .
This is an unfortunate historical side-effect which should be fixed in time
with proper localisation, and should not deter from
.BR rpmatch ()
being the proper way to distinguish between binary answers.
.SH EXAMPLES
The following program displays the results when
.BR rpmatch ()
is applied to the string given in the program's command-line argument.
.PP
.\" SRC BEGIN (rpmatch.c)
.EX
#define _DEFAULT_SOURCE
#include <locale.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
int
main(int argc, char *argv[])
{
if (argc != 2 || strcmp(argv[1], "\-\-help") == 0) {
fprintf(stderr, "%s response\en", argv[0]);
exit(EXIT_FAILURE);
}
setlocale(LC_ALL, "");
printf("rpmatch() returns: %d\en", rpmatch(argv[1]));
exit(EXIT_SUCCESS);
}
.EE
.\" SRC END
.SH SEE ALSO
.BR fgets (3),
.BR getline (3),
.BR nl_langinfo (3),
.BR regcomp (3),
.BR setlocale (3)
|
