~mdw
/
sod
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
3d0d9e3
)
doc/concepts.tex: Fix garbled fragment ordering rules.
author
Mark Wooding
<mdw@distorted.org.uk>
Tue, 15 May 2018 09:49:05 +0000
(10:49 +0100)
committer
Mark Wooding
<mdw@distorted.org.uk>
Fri, 8 Jun 2018 18:58:40 +0000
(19:58 +0100)
doc/concepts.tex
patch
|
blob
|
blame
|
history
diff --git
a/doc/concepts.tex
b/doc/concepts.tex
index
14ae4e0
..
0f4b336
100644
(file)
--- 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
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|
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
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
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