From 443edfd0f6a4bfdb40edc4152730578a2b38bcfe Mon Sep 17 00:00:00 2001 From: Gareth Rees Date: Tue, 30 Oct 2012 17:18:44 +0000 Subject: [PATCH] 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 --- mps/manual/source/guide/overview.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/mps/manual/source/guide/overview.rst b/mps/manual/source/guide/overview.rst index 5a22856c4f1..b8206fb6518 100644 --- a/mps/manual/source/guide/overview.rst +++ b/mps/manual/source/guide/overview.rst @@ -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 ` (you must call :c:func:`mps_free` to return a -block of memory to the pool) and others are :term:`automatically -managed ` (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 ` (the +:term:`garbage collector` reclaims :term:`unreachable` blocks). See +:ref:`pool`. :term:`Formatted ` pools need you to tell them how to **scan** for :term:`references` to allocated blocks. See