X-Git-Url: https://ncurses.scripts.mit.edu/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fhtml%2Fman%2Fcurs_scanw.3x.html;h=19a8e6550e528d54db8731744b79e2693d25577a;hb=4c9f63c460cb7134f142aa65f6866c175ed77605;hp=8bbd242fa1f061b80a84412bd22dd6e8a21b7e3e;hpb=c0f109a299a82a33c16bd7af942a12ce9aefaaf0;p=ncurses.git diff --git a/doc/html/man/curs_scanw.3x.html b/doc/html/man/curs_scanw.3x.html index 8bbd242f..19a8e655 100644 --- a/doc/html/man/curs_scanw.3x.html +++ b/doc/html/man/curs_scanw.3x.html @@ -1,6 +1,6 @@ - @@ -36,7 +36,7 @@ curs_scanw 3x - +

curs_scanw 3x

@@ -54,14 +54,15 @@

SYNOPSIS

        #include <curses.h>
 
-       int scanw(const char *fmt, ...);
-       int wscanw(WINDOW *win, const char *fmt, ...);
-       int mvscanw(int y, int x, const char *fmt, ...);
-       int mvwscanw(WINDOW *win, int y, int x, const char *fmt, ...);
-       int vw_scanw(WINDOW *win, const char *fmt, va_list varglist);
+       int scanw(const char *fmt, ...);
+       int wscanw(WINDOW *win, const char *fmt, ...);
+       int mvscanw(int y, int x, const char *fmt, ...);
+       int mvwscanw(WINDOW *win, int y, int x, const char *fmt, ...);
+
+       int vw_scanw(WINDOW *win, const char *fmt, va_list varglist);
 
        /* obsolete */
-       int vwscanw(WINDOW *win, const char *fmt, va_list varglist);
+       int vwscanw(WINDOW *win, const char *fmt, va_list varglist);

DESCRIPTION

@@ -73,7 +74,7 @@
 
        The vwscanw and vw_scanw routines are  analogous  to  vscanf(3).   They
        perform a wscanw using a variable argument list.  The third argument is
-       a va_list, a pointer to a list of arguments, as defined in <stdarg.h>.
+       a va_list, a pointer to a list of arguments, as defined in <stdarg.h>.

RETURN VALUE

@@ -92,12 +93,12 @@

HISTORY

        While  scanw  was implemented in 4BSD, none of the BSD releases used it
        until 4.4BSD (in a game).  That early version of curses was before  the
-       ANSI  C  standard.   It did not use <varargs.h>, though that was avail-
-       able.  In 1991 (a couple of years after SVr4 was  generally  available,
-       and  after  the C standard was published), other developers updated the
-       library, using <stdarg.h> internally in 4.4BSD curses.  Even with  this
-       improvement,  BSD  curses  did  not  use  function  prototypes (or even
-       declare functions) in the <curses.h> header until 1992.
+       ANSI  C  standard.   It  did  not  use  <varargs.h>,  though  that  was
+       available.  In 1991  (a  couple  of  years  after  SVr4  was  generally
+       available,  and  after  the C standard was published), other developers
+       updated the library, using  <stdarg.h>  internally  in  4.4BSD  curses.
+       Even  with this improvement, BSD curses did not use function prototypes
+       (or even declare functions) in the <curses.h> header until 1992.
 
        SVr2 documented scanw, wscanw tersely as  "scanf  through  stdscr"  and
        tersely as "scanf through win", respectively.
@@ -107,9 +108,9 @@
        be  output  from  scanf(3) would instead be output using waddstr on the
        given window.  SVr3 also added vwscanw, saying that the third parameter
        is  a  va_list, defined in <varargs.h>, and referring the reader to the
-       manual  pages  for  varargs  and  vprintf  for  detailed  descriptions.
-       (Because the SVr3 documentation does not mention vscanf, that reference
-       to vprintf may not be an error).
+       manual  pages  for  varargs  and  vprintf  for  detailed  descriptions.
+       (Because the SVr3 documentation does not mention vscanf, that reference
+       to vprintf may not be an error).
 
        SVr4  added  no  new  variations  of  scanw,  but  provided  for  using
        <varargs.h> or <stdarg.h> to define the va_list type.
@@ -143,16 +144,16 @@
            is  probably  an  editing error which was introduced in XSI, rather
            than being done intentionally.
 
-       o   This implementation returns the number of items scanned,  for  com-
-           patibility  with  SVr4  curses.   As  of  2018,  NetBSD curses also
+       o   This implementation  returns  the  number  of  items  scanned,  for
+           compatibility  with  SVr4  curses.   As of 2018, NetBSD curses also
            returns the number of  items  scanned.   Both  ncurses  and  NetBSD
            curses call vsscanf to scan the string, which returns EOF on error.
 
        o   Portable  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"  con-
-           version  at  the  end of the format string to ensure that something
+           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.