mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-01-12 22:40:46 -08:00
Mps_free is not the only way to manually return memory to a pool (there's also mps_ap_frame_pop in some pools).
Copied from Perforce Change: 180170 ServerID: perforce.ravenbrook.com
This commit is contained in:
parent
b230030681
commit
443edfd0f6
1 changed files with 5 additions and 4 deletions
|
|
@ -73,10 +73,11 @@ available to your program. See :ref:`topic-pool`.
|
|||
|
||||
Pools belong to **pool classes** that specify policies for how their
|
||||
memory is managed. Some pools are :term:`manually managed <manual
|
||||
memory management>` (you must call :c:func:`mps_free` to return a
|
||||
block of memory to the pool) and others are :term:`automatically
|
||||
managed <automatic memory management>` (the :term:`garbage collector`
|
||||
reclaims :term:`unreachable` blocks). See :ref:`pool`.
|
||||
memory management>` (you must explicitly return memory to the pool,
|
||||
for example by calling :c:func:`mps_free`) and others are
|
||||
:term:`automatically managed <automatic memory management>` (the
|
||||
:term:`garbage collector` reclaims :term:`unreachable` blocks). See
|
||||
:ref:`pool`.
|
||||
|
||||
:term:`Formatted <formatted object>` pools need you to tell them how to
|
||||
**scan** for :term:`references` to allocated blocks. See
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue