X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_printw.3x.html;h=6028260530ea0b9f1adc3631ee4f6918b78f7329;hp=203eb0e77de32e0424dbe4a7c4b134d58ee41ad0;hb=81304798ee736c467839c779c9ca5dca48db7bea;hpb=9f479192e3ca3413d235c66bf058f8cc63764898 diff --git a/doc/html/man/curs_printw.3x.html b/doc/html/man/curs_printw.3x.html index 203eb0e7..60282605 100644 --- a/doc/html/man/curs_printw.3x.html +++ b/doc/html/man/curs_printw.3x.html @@ -34,51 +34,51 @@
--curs_printw(3X) curs_printw(3X) +curs_printw(3x) curs_printw(3x)
- printw, wprintw, mvprintw, mvwprintw, vwprintw, vw_printw - print - formatted output in curses windows + printw, wprintw, mvprintw, mvwprintw, vwprintw, vw_printw - print + formatted output in curses windows
- #include <curses.h> + #include <curses.h> - int printw(const char *fmt, ...); - int wprintw(WINDOW *win, const char *fmt, ...); - int mvprintw(int y, int x, const char *fmt, ...); - int mvwprintw(WINDOW *win, int y, int x, const char *fmt, ...); - int vw_printw(WINDOW *win, const char *fmt, va_list varglist); + int printw(const char *fmt, ...); + int wprintw(WINDOW *win, const char *fmt, ...); + int mvprintw(int y, int x, const char *fmt, ...); + int mvwprintw(WINDOW *win, int y, int x, const char *fmt, ...); + int vw_printw(WINDOW *win, const char *fmt, va_list varglist); /* obsolete */ - int vwprintw(WINDOW *win, const char *fmt, va_list varglist); + int vwprintw(WINDOW *win, const char *fmt, va_list varglist);
- The printw, wprintw, mvprintw and mvwprintw routines are analogous to - printf [see printf(3)]. In effect, the string that would be output by - printf is output instead as though waddstr were used on the given win- + The printw, wprintw, mvprintw and mvwprintw routines are analogous to + printf [see printf(3)]. In effect, the string that would be output by + printf is output instead as though waddstr were used on the given win- dow. - The vwprintw and vw_printw routines are analogous to vprintf [see - printf(3)] and perform a wprintw using a variable argument list. The - third argument is a va_list, a pointer to a list of arguments, as de- - fined in <stdarg.h>. + The vwprintw and vw_printw routines are analogous to vprintf [see + printf(3)] and perform a wprintw using a variable argument list. The + third argument is a va_list, a pointer to a list of arguments, as de- + fined in <stdarg.h>.
- Routines that return an integer return ERR upon failure and OK (SVr4 - only specifies "an integer value other than ERR") upon successful com- + Routines that return an integer return ERR upon failure and OK (SVr4 + only specifies "an integer value other than ERR") upon successful com- pletion. X/Open defines no error conditions. In this implementation, an error @@ -87,12 +87,12 @@ is null. Functions with a "mv" prefix first perform a cursor movement using - wmove, and return an error if the position is outside the window, or if + wmove, and return an error if the position is outside the window, or if the window pointer is null.
- While printw was implemented in 4BSD, it was unused until 4.2BSD (which + While printw was implemented in 4BSD, it was unused until 4.2BSD (which used it in games). That early version of curses was before the 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 @@ -101,48 +101,48 @@ ment, BSD curses did not use function prototypes (or even declare func- tions) in the <curses.h> header until 1992. - SVr2 documented printw, wprintw tersely as "printf on stdscr" and - tersely as "printf on win", respectively. + SVr2 documented printw, wprintw tersely as "printf on stdscr" and + tersely as "printf on win", respectively. - SVr3 added mvprintw, and mvwprintw, with a three-line summary saying - that they were analogous to printf(3), explaining that the string which - would be output from printf(3) would instead be output using waddstr on - the given window. SVr3 also added vwprintw, saying that the third pa- - rameter is a va_list, defined in <varargs.h>, and referring the reader - to the manual pages for varargs and vprintf for detailed descriptions. + SVr3 added mvprintw, and mvwprintw, with a three-line summary saying + that they were analogous to printf(3), explaining that the string which + would be output from printf(3) would instead be output using waddstr on + the given window. SVr3 also added vwprintw, saying that the third pa- + rameter is a va_list, defined in <varargs.h>, and referring the reader + to the manual pages for varargs and vprintf for detailed descriptions. - SVr4 added no new variations of printw, but provided for using - <varargs.h> or <stdarg.h> to define the va_list type. + SVr4 added no new variations of printw, but provided for using + <varargs.h> or <stdarg.h> to define the va_list type. - X/Open Curses added vw_printw to replace vwprintw, stating that its - va_list definition requires <stdarg.h>. + X/Open Curses added vw_printw to replace vwprintw, stating that its + va_list definition requires <stdarg.h>.
- In this implementation, vw_printw and vwprintw are equivalent, to sup- - port legacy applications. However, the latter (vwprintw) is obsolete: + In this implementation, vw_printw and vwprintw are equivalent, to sup- + port legacy applications. However, the latter (vwprintw) is obsolete: - o The XSI Curses standard, Issue 4 described these functions. The - function vwprintw is marked TO BE WITHDRAWN, and is to be replaced - by a function vw_printw using the <stdarg.h> interface. + o The XSI Curses standard, Issue 4 described these functions. The + function vwprintw is marked TO BE WITHDRAWN, and is to be replaced + by a function vw_printw using the <stdarg.h> interface. - o The Single Unix Specification, Version 2 states that vw_printw is - preferred to vwprintw since the latter requires including - <varargs.h>, which cannot be used in the same file as <stdarg.h>. - This implementation uses <stdarg.h> for both, because that header - is included in <curses.h>. + o The Single Unix Specification, Version 2 states that vw_printw is + preferred to vwprintw since the latter requires including + <varargs.h>, which cannot be used in the same file as <stdarg.h>. + This implementation uses <stdarg.h> for both, because that header + is included in <curses.h>. - o X/Open Curses, Issue 5 (December 2007) marked vwprintw (along with - vwscanw and the termcap interface) as withdrawn. + o X/Open Curses, Issue 5 (December 2007) marked vwprintw (along with + vwscanw and the termcap interface) as withdrawn.
- curses(3X), curs_addstr(3X), curs_scanw(3X), curs_termcap(3X), - printf(3), vprintf(3). + curses(3x), curs_addstr(3x), curs_scanw(3x), curs_termcap(3x), + printf(3), vprintf(3). - curs_printw(3X) + curs_printw(3x)