ncurses 6.0 - patch 20180121

[ncurses.git] / man / curs_scanw.3x

diff --git a/man/curs_scanw.3x b/man/curs_scanw.3x
index 85a8ae32be5195e95ff2c32ab538ab1e32e4cb45..a502d93350ab6bd2eb5b147dff3d77d6253ca7ba 100644 (file)
--- a/man/curs_scanw.3x
+++ b/man/curs_scanw.3x
@@ -26,7 +26,7 @@
 .\" authorization.                                                           *
 .\"***************************************************************************
 .\"
-.\" $Id: curs_scanw.3x,v 1.18 2017/04/17 00:07:02 tom Exp $
+.\" $Id: curs_scanw.3x,v 1.19 2017/11/21 00:46:31 tom Exp $
 .TH curs_scanw 3X ""
 .SH NAME
 \fBscanw\fR,
@@ -82,13 +82,13 @@ This implementation uses \fB<stdarg.h>\fR for both, because that header
 is included in \fB<curses.h\fR>.
 .LP
 Both XSI and The Single Unix Specification, Version 2 state that these
-functions return ERR or OK.
+functions return \fBERR\fP or \fBOK\fP.
 Since the underlying \fBscanf\fR(3) can return the number of items scanned,
 and the SVr4 code was documented to use this feature,
 this is probably an editing error which was introduced in XSI,
 rather than being done intentionally.
-Portable applications should only test if the return value is ERR,
-since the OK value (zero) is likely to be misleading.
+Portable applications should only test if the return value is \fBERR\fP,
+since the \fBOK\fP value (zero) is likely to be misleading.
 One possible way to get useful results would be to use a "%n" conversion
 at the end of the format string to ensure that something was processed.
 .SH SEE ALSO