mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-27 15:52:00 -08:00
Arenainit and arenafinish no longer exist under those names, and there is no longer anything special about them, so remove design documentation.
BufferFinishMethod and BufferDescribeMethod were removed, so remove the design documentation for them. Copied from Perforce Change: 192179 ServerID: perforce.ravenbrook.com
This commit is contained in:
parent
c898410a63
commit
ba8ac77fef
2 changed files with 0 additions and 20 deletions
|
|
@ -202,12 +202,6 @@ arguments to ``mps_arena_create_k()`` are class-dependent.
|
|||
|
||||
.. _design.mps.protocol: protocol
|
||||
|
||||
_`.class.init`: However, the generic ``ArenaInit()`` is called from the
|
||||
class-specific method, rather than vice versa, because the method is
|
||||
responsible for allocating the memory for the arena descriptor and the
|
||||
arena lock in the first place. Likewise, ``ArenaFinish()`` is called
|
||||
from the finish method.
|
||||
|
||||
_`.class.fields`: The ``grainSize`` (for allocation and freeing) and
|
||||
``zoneShift`` (for computing zone sizes and what zone an address is
|
||||
in) fields in the arena are the responsibility of the each class, and
|
||||
|
|
|
|||
|
|
@ -212,13 +212,6 @@ class-specific behaviour. _`.replay.init`: The ``init()`` method
|
|||
should emit a ``BufferInit<foo>`` event (if there aren't any extra
|
||||
parameters, ``<foo> = ""``).
|
||||
|
||||
``typedef void (*BufferFinishMethod)(Buffer buffer)``
|
||||
|
||||
_`.class.method.finish`: ``finish()`` is a class-specific finish
|
||||
method called from ``BufferFinish()``. Client-defined methods must
|
||||
call their superclass method (via a next-method call) after performing
|
||||
any class-specific behaviour.
|
||||
|
||||
``typedef void (*BufferAttachMethod)(Buffer buffer, Addr base, Addr limit, Addr init, Size size)``
|
||||
|
||||
_`.class.method.attach`: ``attach()`` is a class-specific method
|
||||
|
|
@ -256,13 +249,6 @@ setter method which sets the rank set of a buffer. It is called from
|
|||
``BufferSetRankSet()``. Clients should not need to define their own
|
||||
methods for this.
|
||||
|
||||
``typedef Res (*BufferDescribeMethod)(Buffer buffer, mps_lib_FILE *stream, Count depth)``
|
||||
|
||||
_`.class.method.describe`: ``describe()`` is a class-specific method
|
||||
called to describe a buffer, via ``BufferDescribe()``. Client-defined
|
||||
methods must call their superclass method (via a next-method call)
|
||||
before describing any class-specific state.
|
||||
|
||||
|
||||
Logging
|
||||
-------
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue