- The XSI Curses standard, Issue 4 describes these func-
- tions. The function <STRONG>vwscanw</STRONG> is marked TO BE WITHDRAWN,
- and is to be replaced by a function <STRONG>vw_scanw</STRONG> using the
- <STRONG><stdarg.h></STRONG> interface. The Single Unix Specification, Ver-
- sion 2 states that <STRONG>vw_scanw</STRONG> is preferred to <STRONG>vwscanw</STRONG> since
- the latter requires including <STRONG><varargs.h></STRONG>, which cannot be
- used in the same file as <STRONG><stdarg.h></STRONG>. This implementation
- uses <STRONG><stdarg.h></STRONG> for both, because that header is included
- in <STRONG><curses.h</STRONG>>.
-
- Both XSI and The Single Unix Specification, Version 2
- state that these functions return ERR or OK. Since the
- underlying <STRONG>scanf(3)</STRONG> can return the number of items
- scanned, and the SVr4 code was documented to use this fea-
- ture, this is probably an editing error which was intro-
- duced in XSI, rather than being done intentionally. Por-
- table applications should only test if the return value is
- ERR, since the OK 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.
+ The XSI Curses standard, Issue 4 describes these functions. The func-
+ tion <STRONG>vwscanw</STRONG> is marked TO BE WITHDRAWN, and is to be replaced by a
+ function <STRONG>vw_scanw</STRONG> using the <STRONG><stdarg.h></STRONG> interface. The Single Unix
+ Specification, Version 2 states that <STRONG>vw_scanw</STRONG> is preferred to <STRONG>vwscanw</STRONG>
+ since the latter requires including <STRONG><varargs.h></STRONG>, which cannot be used
+ in the same file as <STRONG><stdarg.h></STRONG>. This implementation uses <STRONG><stdarg.h></STRONG>
+ for both, because that header is included in <STRONG><curses.h</STRONG>>.
+
+ Both XSI and The Single Unix Specification, Version 2 state that these
+ functions return <STRONG>ERR</STRONG> or <STRONG>OK</STRONG>. Since the underlying <STRONG>scanf(3)</STRONG> 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 <STRONG>ERR</STRONG>, since the <STRONG>OK</STRONG> 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.