+ Any implementation of curses must not free the memory associated with a
+ screen, since (even after calling <B><A HREF="curs_initscr.3X.html">endwin(3X)</A></B>), it must be available for
+ use in the next call to <B><A HREF="curs_refresh.3X.html">refresh(3X)</A></B>. There are also chunks of memory
+ held for performance reasons. That makes it hard to analyze curses ap-
+ plications for memory leaks. When using the specially configured de-
+ bugging version of the ncurses library, applications can call functions
+ which free those chunks of memory, simplifying the process of memory-
+ leak checking.
+
+ Some of the functions are named with a "_nc_" prefix because they are
+ not intended for use in the non-debugging library:
+
+ <B>_nc_freeall</B>
+ This frees (almost) all of the memory allocated by ncurses.
+
+ <B>_nc_free_and_exit</B>
+ This frees the memory allocated by ncurses (like <B>_nc_freeall</B>), and
+ exits the program. It is preferred over <B>_nc_freeall</B> since some of
+ that memory may be required to keep the application running. Sim-
+ ply exiting (with the given exit-code) is safer.
+
+ <B>_nc_free_tinfo</B>
+ Use this function if only the low-level terminfo functions (and
+ corresponding library) are used. Like <B>_nc_free_and_exit</B>, it exits
+ the program after freeing memory.
+
+ The functions prefixed "_nc" are normally not available; they must be
+ configured into the library at build time using the <B>--disable-leaks</B> op-
+ tion. That compiles-in code that frees memory that normally would not
+ be freed.
+
+ The <B>exit_curses</B> and <B>exit_terminfo</B> functions call <B>_nc_free_and_exit</B> and
+ <B>_nc_free_tinfo</B> if the library is configured to support memory-leak
+ checking. If the library is not configured to support memory-leak
+ checking, they simply call <B>exit</B>.
+
+
+</PRE><H2><a name="h2-RETURN-VALUE">RETURN VALUE</a></H2><PRE>