X-Git-Url: https://ncurses.scripts.mit.edu/?a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_memleaks.3x.html;fp=doc%2Fhtml%2Fman%2Fcurs_memleaks.3x.html;h=2f8490224b51d4f8a7049ab73a7d418812db0267;hb=31c4bcf3307145fc5368b4aaf15e41bdd66a984b;hp=95ed8cf7423a6fe9d93d530f5710dd2e2eafcb02;hpb=2035f48ed0fc56ec4e5caf9b7c10e00ba43e160f;p=ncurses.git diff --git a/doc/html/man/curs_memleaks.3x.html b/doc/html/man/curs_memleaks.3x.html index 95ed8cf7..2f849022 100644 --- a/doc/html/man/curs_memleaks.3x.html +++ b/doc/html/man/curs_memleaks.3x.html @@ -1,6 +1,6 @@ -curs_memleaks 3x 2022-06-04 ncurses 6.4 Library calls +curs_memleaks 3x 2023-09-16 ncurses 6.4 Library calls -

curs_memleaks 3x 2022-06-04 ncurses 6.4 Library calls

+

curs_memleaks 3x 2023-09-16 ncurses 6.4 Library calls

 curs_memleaks(3x)                Library calls               curs_memleaks(3x)
 
@@ -47,7 +47,7 @@

NAME

-       exit_curses, exit_terminfo - curses memory-leak checking
+       exit_curses, exit_terminfo - check for memory leaks in curses

SYNOPSIS

@@ -70,11 +70,11 @@
        Any implementation of curses must not free the memory associated with a
        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.
+       held  for  performance  reasons.   That makes it hard to analyze curses
+       applications 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.
 
        Some  of  the functions are named with a "_nc_" prefix because they are
        not intended for use in the non-debugging library:
@@ -85,8 +85,8 @@
        _nc_free_and_exit
             This frees the memory allocated by ncurses (like _nc_freeall), and
             exits the program.  It is preferred over _nc_freeall since some of
-            that memory may be required to keep the application running.  Sim-
-            ply exiting (with the given exit-code) is safer.
+            that memory may be  required  to  keep  the  application  running.
+            Simply exiting (with the given exit-code) is safer.
 
        _nc_free_tinfo
             Use  this  function  if only the low-level terminfo functions (and
@@ -94,9 +94,9 @@
             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 --disable-leaks op-
-       tion.   That compiles-in code that frees memory that normally would not
-       be freed.
+       configured into the library at build  time  using  the  --disable-leaks
+       option.   That  compiles-in  code that frees memory that normally would
+       not be freed.
 
        The exit_curses and exit_terminfo functions call _nc_free_and_exit  and
        _nc_free_tinfo  if  the  library  is  configured to support memory-leak
@@ -109,8 +109,8 @@

PORTABILITY

-       These functions are not part of X/Open Curses; nor do other implementa-
-       tions of curses provide a similar feature.
+       These   functions   are  not  part  of  X/Open  Curses;  nor  do  other
+       implementations of curses provide a similar feature.
 
        In any implementation of X/Open Curses, an application can free part of
        the memory allocated by curses:
@@ -132,7 +132,7 @@
 
 
 
-ncurses 6.4                       2022-06-04                 curs_memleaks(3x)
+ncurses 6.4                       2023-09-16                 curs_memleaks(3x)