X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_memleaks.3x.html;h=62f03549d12f2ae9745e727d133a9ff3d9231b91;hp=252a9807a6fc9e25386fc3e67078ff53d1b48230;hb=7503e8d82292a2a0a4d8bb55bdf3f8a203159f68;hpb=c55d387cebf1cee4757ca2c2ef4fbeae59ee4175;ds=sidebyside
diff --git a/doc/html/man/curs_memleaks.3x.html b/doc/html/man/curs_memleaks.3x.html
index 252a9807..62f03549 100644
--- a/doc/html/man/curs_memleaks.3x.html
+++ b/doc/html/man/curs_memleaks.3x.html
@@ -1,6 +1,7 @@
@@ -67,13 +68,13 @@
ncurses library.
Any implementation of curses must not free the memory associated with a
- screen, since (even after calling endwin), it must be available for use
- in the next call to refresh(3x). There are also chunks of memory held
- for performance reasons. That makes it hard to analyze curses applica-
- tions for memory leaks. When using the specially configured debugging
- version of the ncurses library, applications can call functions which
- free those chunks of memory, simplifying the process of memory-leak
- checking.
+ screen, since (even after calling endwin(3x)), it must be available for
+ use in the next call to refresh(3x). 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: