+ Other implementions may not declare the capability name
+ arrays. Some provide them without declaring them. X/Open
+ does not specify them.
+
+ Extended terminal capability names, e.g., as defined by
+ <STRONG>tic</STRONG> <STRONG>-x</STRONG>, are not stored in the arrays described here.
+
+
+</PRE><H3><a name="h3-Output-buffering">Output buffering</a></H3><PRE>
+ Older versions of <STRONG>ncurses</STRONG> assumed that the file descriptor
+ passed to <STRONG>setupterm</STRONG> from <STRONG>initscr</STRONG> or <STRONG>newterm</STRONG> uses buffered
+ I/O, and would write to the corresponding stream. In ad-
+ dition to the limitation that the terminal was left in
+ block-buffered mode on exit (like System V curses), it was
+ problematic because <STRONG>ncurses</STRONG> did not allow a reliable way
+ to cleanup on receiving SIGTSTP.
+
+ The current version (ncurses6) uses output buffers managed
+ directly by <STRONG>ncurses</STRONG>. Some of the low-level functions de-
+ scribed in this manual page write to the standard output.
+ They are not signal-safe. The high-level functions in
+ <STRONG>ncurses</STRONG> use alternate versions of these functions using
+ the more reliable buffering scheme.
+
+
+</PRE><H3><a name="h3-Function-prototypes">Function prototypes</a></H3><PRE>
+ The X/Open Curses prototypes are based on the SVr4 curses
+ header declarations, which were defined at the same time
+ the C language was first standardized in the late 1980s.
+
+ <STRONG>o</STRONG> X/Open Curses uses <STRONG>const</STRONG> less effectively than a later
+ design might, in some cases applying it needlessly to
+ values are already constant, and in most cases over-
+ looking parameters which normally would use <STRONG>const</STRONG>.
+ Using constant parameters for functions which do not
+ use <STRONG>const</STRONG> may prevent the program from compiling. On
+ the other hand, <EM>writable</EM> <EM>strings</EM> are an obsolescent
+ feature.
+
+ As an extension, this implementation can be configured
+ to change the function prototypes to use the <STRONG>const</STRONG>
+ keyword. The ncurses ABI 6 enables this feature by
+ default.
+
+ <STRONG>o</STRONG> X/Open Curses prototypes <STRONG>tparm</STRONG> with a fixed number of
+ parameters, rather than a variable argument list.
+
+ This implementation uses a variable argument list, but
+ can be configured to use the fixed-parameter list.
+ Portable applications should provide 9 parameters af-
+ ter the format; zeroes are fine for this purpose.
+
+ In response to review comments by Thomas E. Dickey,
+ X/Open Curses Issue 7 proposed the <STRONG>tiparm</STRONG> function in
+ mid-2009.
+
+
+</PRE><H3><a name="h3-Special-TERM-treatment">Special TERM treatment</a></H3><PRE>
+ If configured to use the terminal-driver, e.g., for the
+ MinGW port,
+
+ <STRONG>o</STRONG> <STRONG>setupterm</STRONG> interprets a missing/empty TERM variable as
+ the special value "unknown".
+
+ <STRONG>o</STRONG> <STRONG>setupterm</STRONG> allows explicit use of the the windows con-
+ sole driver by checking if $TERM is set to "#win32con"
+ or an abbreviation of that string.
+
+
+</PRE><H3><a name="h3-Other-portability-issues">Other portability issues</a></H3><PRE>