curses_intro.3x (2010 09)

c
curses_intro(3X) curses_intro(3X)
(X/Open CURSES)
visible all library functions referenced in this specification and labelled
ENHANCED CURSES.
An application that uses any API specified as ENHANCED CURSES must define
_XOPEN_SOURCE_EXTENDED = 1
in each source file or as part of its compilation environment. When
_XOPEN_SOURCE_EXTENDED = 1
is defined in a source file, it must appear before any header is
included.
If the implementation supports the utilities marked DEVELOPMENT in the Curses Specification , the
lint utility recognises the additional -l curses
operand for standard libraries:
-l curses
Names the library llib-lcurses.ln
, which will contain functions specified in
this document.
It is unspecified whether the library
llib-lcurses.ln exists as a regular file.
The X/Open Name Space (ENHANCED CURSES)
The requirements in this section are in effect only for implementations that claim Enhanced Curses com-
pliance.
All identifiers in this document are defined in at least one of the headers
<curses.h>, <term.h>,
<unctrl.h>. When _XOPEN_SOURCE
is defined, each header defines or declares some identifiers,
potentially conflicting with identifiers used by the application. The set of identifiers visible to the applica-
tion consists of precisely those identifiers from the header pages of the included headers, as well as addi-
tional identifiers reserved for the implementation. In addition, some headers may make visible
identifiers from other headers as indicated on the relevant header pages.
The identifiers reserved for use by the implementation are described below.
1 Each identifier with external linkage described in the header section is reserved for use as an
identifier with external linkage if the header is included.
2 Each macro name described in the header section is reserved for any use if the header is
included.
3 Each identifier with file scope described in the header section is reserved for use as an
identifier with file scope in the same name space if the header is included.
4 All identifiers consisting of exactly 2 uppercase letters.
If any header in the following table is included, identifiers with the prefixes, suffixes or complete names
shown are reserved for use by the implementation.
Complete
Name
Header Prefix Suffix
add, attr, get, in, mousr, mv, scr, slk, un,
wadd, wattr, wbkg, win
<curses.h>
ANY header _t
If any header in the following table is included, macros with the prefixes shown may be defined. After the
last inclusion of a given header, an application may use identifiers with the corresponding prefixes for its
own purpose, provided their use is preceded by an #undef of the corresponding macro.
Header Prefix
A_, ACS_, ALL_, BUTTON, COLOR_, KEY_, MOUSE,
REPORT_, WA_, WACS_
<curses.h>
<term.h> ext_
The following identifiers are reserved, regardless of the inclusion of headers:
1 All identifiers that begin with an underscore and either an uppercase letter or another under-
score are always reserved for any use by the implementation.
2 All identifiers that begin with an underscore are always reserved for use as identifiers with file
scope in both the ordinary identifier and tag name spaces.
3 All identifiers listed as reserved in the X/Open System Interfaces and Headers, Issue 4, Ver-
sion 2 specification are reserved for use as identifiers with external linkage.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010