|
Lines 103-109
Link Here
|
| 103 |
routines are \fBmove\fR and \fBaddch\fR. More general versions of |
103 |
routines are \fBmove\fR and \fBaddch\fR. More general versions of |
| 104 |
these routines are included with names beginning with \fBw\fR, |
104 |
these routines are included with names beginning with \fBw\fR, |
| 105 |
allowing the user to specify a window. The routines not beginning |
105 |
allowing the user to specify a window. The routines not beginning |
| 106 |
with \fBw\fR affect \fBstdscr\fR.) |
106 |
with \fBw\fR affect \fBstdscr\fR. |
| 107 |
|
107 |
|
| 108 |
After using routines to manipulate a window, \fBrefresh\fR is called, |
108 |
After using routines to manipulate a window, \fBrefresh\fR is called, |
| 109 |
telling \fBcurses\fR to make the user's CRT screen look like |
109 |
telling \fBcurses\fR to make the user's CRT screen look like |
|
Lines 159-165
Link Here
|
| 159 |
which is used for certain low-level operations like clearing and redrawing a |
159 |
which is used for certain low-level operations like clearing and redrawing a |
| 160 |
screen containing garbage. The \fBcurscr\fR can be used in only a few |
160 |
screen containing garbage. The \fBcurscr\fR can be used in only a few |
| 161 |
routines. |
161 |
routines. |
| 162 |
|
|
|
| 163 |
.SS Routine and Argument Names |
162 |
.SS Routine and Argument Names |
| 164 |
Many \fBcurses\fR routines have two or more versions. The routines prefixed |
163 |
Many \fBcurses\fR routines have two or more versions. The routines prefixed |
| 165 |
with \fBw\fR require a window argument. The routines prefixed with \fBp\fR |
164 |
with \fBw\fR require a window argument. The routines prefixed with \fBp\fR |
|
Lines 186-192
Link Here
|
| 186 |
\fBchtype\fR. The types \fBWINDOW\fR, \fBSCREEN\fR, \fBbool\fR, and |
185 |
\fBchtype\fR. The types \fBWINDOW\fR, \fBSCREEN\fR, \fBbool\fR, and |
| 187 |
\fBchtype\fR are defined in \fB<curses.h>\fR. The type \fBTERMINAL\fR |
186 |
\fBchtype\fR are defined in \fB<curses.h>\fR. The type \fBTERMINAL\fR |
| 188 |
is defined in \fB<term.h>\fR. All other arguments are integers. |
187 |
is defined in \fB<term.h>\fR. All other arguments are integers. |
| 189 |
|
|
|
| 190 |
.SS Routine Name Index |
188 |
.SS Routine Name Index |
| 191 |
The following table lists each \fBcurses\fR routine and the name of |
189 |
The following table lists each \fBcurses\fR routine and the name of |
| 192 |
the manual page on which it is described. Routines flagged with `*' |
190 |
the manual page on which it is described. Routines flagged with `*' |
|
Lines 719-725
Link Here
|
| 719 |
@DATADIR@/tabset |
717 |
@DATADIR@/tabset |
| 720 |
directory containing initialization files for the terminal capability database |
718 |
directory containing initialization files for the terminal capability database |
| 721 |
/usr/share/misc/terminfo |
719 |
/usr/share/misc/terminfo |
| 722 |
terminal capability database |
|
|
| 723 |
.SH SEE ALSO |
720 |
.SH SEE ALSO |
| 724 |
\fBterminfo\fR(\*n) and 3X pages whose names begin "curs_" for detailed routine |
721 |
\fBterminfo\fR(\*n) and 3X pages whose names begin "curs_" for detailed routine |
| 725 |
descriptions. |
722 |
descriptions. |
|
Lines 904-910
Link Here
|
| 904 |
ANSI C standard (see section 3.5.4.1), these declarations are either (a) |
901 |
ANSI C standard (see section 3.5.4.1), these declarations are either (a) |
| 905 |
meaningless, or (b) meaningless and illegal. The declaration |
902 |
meaningless, or (b) meaningless and illegal. The declaration |
| 906 |
\fBconst char *x\fR is a modifiable pointer to unmodifiable data, but |
903 |
\fBconst char *x\fR is a modifiable pointer to unmodifiable data, but |
| 907 |
\fBchar *const x\fR' is |
904 |
\fBchar *const x\fR is |
| 908 |
an unmodifiable pointer to modifiable data. Given that C passes arguments by |
905 |
an unmodifiable pointer to modifiable data. Given that C passes arguments by |
| 909 |
value, \fB<type> *const\fR as a formal type is at best dubious. Some compilers |
906 |
value, \fB<type> *const\fR as a formal type is at best dubious. Some compilers |
| 910 |
choke on the prototypes. Therefore, in this implementation, they have been |
907 |
choke on the prototypes. Therefore, in this implementation, they have been |