[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
void wfdbquit(void) |
This function closes all open WFDB files and frees any memory allocated by other WFDB library functions. It also resets the following:
WFDB_DEFGAIN
adu/mV, a quantity defined in `<wfdb/wfdb.h>');
(see section aduphys)
If any annotations have been written out-of-order (see section 5.10 Annotation Order), this function attempts to run `sortann' (see the WFDB Applications Guide) as a subprocess to restore the annotations to canonical order. If this cannot be done, it prints a warning message indicating that the annotations are not in order, and providing instructions for putting them in order.
Programs that do not write annotations or signals need not use
wfdbquit
. Note, however, that several WFDB library functions allocate
memory that is maintained for later use by the library. This is not generally
a problem, since these functions also free such memory if it is no longer
needed on a subsequent call; thus these `memory leaks' do not grow over time.
Virtually all operating systems reclaim memory allocated by user-level
applications on exit, so that a small and self-limiting leak is not
a problem. Nevertheless, there are embedded systems and other
environments in which memory is not reclaimed when a user application
exits, and in these cases it is best to invoke wfdbquit()
on exit from
any WFDB application, even those that do not write output using the
library. In an ANSI/ISO C environment, this can be ensured by
including the line
atexit(wfdbquit); |
early in the code, before the first exit.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |