From 9761db0da830385bcc0fca81f56f24536a46aeda Mon Sep 17 00:00:00 2001 Message-Id: <9761db0da830385bcc0fca81f56f24536a46aeda.1718306323.git.mdw@distorted.org.uk> From: Mark Wooding Date: Sat, 7 May 2016 10:56:54 +0100 Subject: [PATCH] doc/concepts.tex: Don't highlight `primary' as literal, because it's not. Organization: Straylight/Edgeware From: Mark Wooding --- doc/concepts.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/concepts.tex b/doc/concepts.tex index 89dcd8f..b8cdfe9 100644 --- a/doc/concepts.tex +++ b/doc/concepts.tex @@ -541,7 +541,7 @@ defining $N$. The default method combination is called the \emph{standard method combination}; other method combinations are useful occasionally for special effects. The standard method combination accepts four direct method roles, -called @|primary| (the default), @|before|, @|after|, and @|around|. +called `primary' (the default), @|before|, @|after|, and @|around|. All direct methods subject to the standard method combination must have argument lists which \emph{match} the message's argument list: @@ -615,7 +615,7 @@ A typical use for @|around| methods is to allow a base class to set up the dynamic environment appropriately for the primary methods of its subclasses, e.g., by claiming a lock, and restore it afterwards. -The @|next_method| function provided to methods with the @|primary| and +The @|next_method| function provided to methods with the primary and @|around| roles accepts the same arguments, and returns the same type, as the message, except that one or two additional arguments are inserted at the front of the argument list. The first additional argument is always the @@ -626,7 +626,7 @@ second additional argument; otherwise, In the former case, a variable of the argument pointer (so the method body can process the variable argument suffix itself, and still pass a fresh copy on to the next method). -A method with the @|primary| or @|around| role may use the convenience macro +A method with the primary or @|around| role may use the convenience macro @|CALL_NEXT_METHOD|, which takes no arguments itself, and simply calls @|next_method| with appropriate arguments: the receiver @|me| pointer, the argument pointer @|sod__master_ap| (if applicable), and the method's -- [mdw]