#include <term.h> chtype acs_map; SCREEN * SP; TERMINAL * cur_term; char ttytype; NCURSES_CONST char * const boolcodes;
NCURSES_CONST char * const boolfnames;
NCURSES_CONST char * const boolnames; NCURSES_CONST char * const numcodes;
NCURSES_CONST char * const numfnames;
NCURSES_CONST char * const numnames; NCURSES_CONST char * const strcodes;
NCURSES_CONST char * const strfnames;
NCURSES_CONST char * const strnames;
Depending on the configuration, these may be actual variables, or macros (see curs_threads(3X)) which provide read-only access to curses's state. In either case, applications should treat them as read-only to avoid confusing the library.
The encoding of the information in this array has changed periodically. Application developers need only know that it is used for the ``ACS_'' constants in <curses.h>.
The comparable data for the wide-character library is a private variable.
It is possible to save a value of cur_term for subsequent use as a parameter to set_term, for switching between screens. Alternatively, one can save the return value from newterm or setupterm(3X) to reuse in set_term.
The long terminfo capability names use a ``l'' (ell) in their names: boolfnames, numfnames, and strfnames.
These are the short names for terminfo capabilities: boolnames, numnames, and strnames.
These are the corresponding names used for termcap descriptions: boolcodes, numcodes, and strcodes.
In addition to the variables, <term.h> also defines a symbol for each terminfo capability long name. These are in terms of the symbol CUR, which is defined
#define CUR ((TERMTYPE *)(cur_term))->
These symbols provide a faster method of accessing terminfo capabilities than using tigetstr(3X), etc.
The actual definition of CUR depends upon the implementation, but each terminfo library provides these long names defined to point into the current terminal description loaded into memory.
Other implementations may have comparable variables. Some implementations provide the variables in their libraries, but omit them from the header files.
All implementations which provide terminfo interfaces add definitions as described in the Terminfo Names section. Most, but not all, base the definition upon the cur_term variable.