+ impact portability to other implementations:
+
+ <STRONG>o</STRONG> SVr4 curses stores the <EM>static</EM> variables in the <STRONG>TERMINAL</STRONG>
+ structure (declared in <STRONG>term.h</STRONG>), and the <EM>dynamic</EM> <EM>variables</EM> on
+ the stack in the <STRONG>tparm</STRONG> function. The former are zeroed
+ automatically when the <STRONG>setupterm</STRONG> function allocates the data.
+ The latter are set only by a <STRONG>%P</STRONG> operator. A <STRONG>%g</STRONG> for a given
+ variable without first setting it with <STRONG>%P</STRONG> will give
+ unpredictable results.
+
+ <STRONG>o</STRONG> Solaris XPG4 curses does not distinguish between <EM>dynamic</EM> and
+ <EM>static</EM> variables. They are the same. Like SVr4 curses, XPG4
+ curses does not initialize these explicitly.
+
+ <STRONG>o</STRONG> Before version 6.3, ncurses stores both <EM>dynamic</EM> and <EM>static</EM>
+ variables in persistent storage, initialized to zeros.
+
+ <STRONG>o</STRONG> Beginning with version 6.3, ncurses stores <EM>static</EM> and <EM>dynamic</EM>
+ variables in the same manner as SVr4. Unlike other
+ implementations, ncurses zeros dynamic variables before the
+ first <STRONG>%g</STRONG> or <STRONG>%P</STRONG> operator.