- This implementation also provides <STRONG>getbegx</STRONG>, <STRONG>getbegy</STRONG>,
- <STRONG>getcurx</STRONG>, <STRONG>getcury</STRONG>, <STRONG>getmaxx</STRONG>, <STRONG>getmaxy</STRONG>, <STRONG>getparx</STRONG> and <STRONG>getpary</STRONG>
- for compatibility with older versions of curses.
+ This implementation also provides functions <STRONG>getbegx</STRONG>, <STRONG>getb-</STRONG>
+ <STRONG>egy</STRONG>, <STRONG>getcurx</STRONG>, <STRONG>getcury</STRONG>, <STRONG>getmaxx</STRONG>, <STRONG>getmaxy</STRONG>, <STRONG>getparx</STRONG> and <STRONG>get-</STRONG>
+ <STRONG>pary</STRONG> for compatibility with older versions of curses.
+
+ Although X/Open Curses does not address this, many imple-
+ mentations provide members of the WINDOW structure con-
+ taining values corresponding to these macros. For best
+ portability, do not rely on using the data in WINDOW,
+ since some implementations make WINDOW opaque (do not
+ allow direct use of its members).
+
+ Besides the problem of opaque structures, the data stored
+ in like-named members may not have like-values in differ-
+ ent implementations. For example, the WINDOW._maxx and
+ WINDOW._maxy values in ncurses have (at least since
+ release 1.8.1) differed by one from some other implementa-
+ tions. The difference is hidden by means of the macro
+ <STRONG>getmaxyx</STRONG>.