This implementation can be configured to provide rudimentary support
for multi-threaded applications. This makes a different set of li-
- braries, e.g., libncursest since the binary interfaces are different.
+ braries, e.g., libncursest since the binary interfaces are different.
Rather than modify the interfaces to pass a thread specifier to each
function, it adds a few functions which can be used in any configura-
tion which hide the mutex's needed to prevent concurrent use of the
global variables when configured for threading.
- In addition to forcing access to members of the WINDOW structure to be
- via functions (see curs_opaque(3X)), it makes functions of the common
+ In addition to forcing access to members of the WINDOW structure to be
+ via functions (see curs_opaque(3x)), it makes functions of the common
global variables, e.g., COLORS, COLOR_PAIRS, COLS, ESCDELAY, LINES,
TABSIZE curscr, newscr and ttytype. Those variables are maintained as
- read-only values, stored in the SCREEN structure.
+ read-only values, stored in the SCREEN structure.
Even this is not enough to make a thread-safe application using curses.
A multi-threaded application would be expected to have threads updating
@@ -90,14 +90,14 @@
here address these special situations.
The ESCDELAY and TABSIZE global variables are modified by some applica-
- tions. To modify them in any configuration, use the set_escdelay or
- set_tabsize functions. Other global variables are not modifiable.
+ tions. To modify them in any configuration, use the set_escdelay or
+ set_tabsize functions. Other global variables are not modifiable.
- The get_escdelay function returns the value for ESCDELAY.
+ The get_escdelay function returns the value for ESCDELAY.
- The use_window and use_screen functions provide coarse granularity mu-
- texes for their respective WINDOW and SCREEN parameters, and call a us-
- er-supplied function, passing it a data parameter, and returning the
+ The use_window and use_screen functions provide coarse granularity mu-
+ texes for their respective WINDOW and SCREEN parameters, and call a us-
+ er-supplied function, passing it a data parameter, and returning the
value from the user-supplied function to the application.
@@ -106,22 +106,22 @@
tered during operation. In addition, they use data which is maintained
within a hierarchy of scopes.
- o global data, e.g., used in the low-level terminfo or termcap in-
+ o global data, e.g., used in the low-level terminfo or termcap in-
terfaces.
- o terminal data, e.g., associated with a call to set_curterm. The
+ o terminal data, e.g., associated with a call to set_curterm. The
terminal data are initialized when screens are created.
- o screen data, e.g., associated with a call to newterm or initscr.
+ o screen data, e.g., associated with a call to newterm or initscr.
- o window data, e.g., associated with a call to newwin or subwin.
+ o window data, e.g., associated with a call to newwin or subwin.
Windows are associated with screens. Pads are not necessarily
associated with a particular screen.
Most curses applications operate on one or more windows within a
single screen.
- o reentrant, i.e., it uses only the data passed as parameters.
+ o reentrant, i.e., it uses only the data passed as parameters.
This table lists the scope of data used for each symbol in the ncurses
library when it is configured to support threading:
@@ -133,7 +133,7 @@
COLOR_PAIR reentrant
COLOR_PAIRS screen (readonly)
COLS screen (readonly)
- ESCDELAY screen (readonly, see set_escdelay)
+ ESCDELAY screen (readonly, see set_escdelay)
LINES screen (readonly)
PAIR_NUMBER reentrant
PC global
@@ -589,7 +589,7 @@