From 13cb243aea114b87d4382b8aaf1d357c9495dc0e Mon Sep 17 00:00:00 2001 Message-Id: <13cb243aea114b87d4382b8aaf1d357c9495dc0e.1715349556.git.mdw@distorted.org.uk> From: Mark Wooding Date: Tue, 15 May 2018 10:49:05 +0100 Subject: [PATCH] doc/concepts.tex: Fix garbled fragment ordering rules. Organization: Straylight/Edgeware From: Mark Wooding --- doc/concepts.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/concepts.tex b/doc/concepts.tex index 14ae4e0..0f4b336 100644 --- a/doc/concepts.tex +++ b/doc/concepts.tex @@ -857,7 +857,7 @@ be executed to set up a new instance. Each superclass's initialization fragments are executed with @|me| bound to an instance pointer of the appropriate superclass type, immediately after that superclass's slots (if any) have been initialized; therefore, fragments defined by a more specific -superclass are executed after fragments defined by a more specific +superclass are executed after fragments defined by a less specific superclass. A class may define more than one initialization fragment: the fragments are executed in the order in which they appear in the class definition. It is possible for an initialization fragment to use @|return| @@ -971,7 +971,7 @@ A class can define \emph{teardown fragments}: pieces of literal code to be executed to shut down an instance. Each superclass's teardown fragments are executed with @|me| bound to an instance pointer of the appropriate superclass type; fragments defined by a more specific superclass are executed -before fragments defined by a more specific superclass. A class may define +before fragments defined by a less specific superclass. A class may define more than one teardown fragment: the fragments are executed in the order in which they appear in the class definition. It is possible for an initialization fragment to use @|return| or @|goto| for special control-flow -- [mdw]