are used as metavariables. The whole is written in the rather stilted
over-formal prose one typically finds in mathematical papers.</para>
-<para>Certain phrasings in the manual suggest that the authors
-thought of flowcharts as the primary notation for programs, and
-considered MAD code a sort of hand-compiled derivative of it. This
-made sense at the time; programming notations were clumsy and
-primitive, and the typical complexity of programs was very low.
-By five years later (roughly three or four Moore's-Law doublings)
-flowcharting was going out of fashion, probably for the simple
-reason that flowcharts were getting too large to draw and read!</para>
+<para>Certain phrasings in the manual suggest that the authors thought
+of flowcharts as the primary notation for programs, and considered MAD
+code a sort of hand-compiled derivative of it. This made sense at the
+time, though it would have made much more sense if the authors had
+actually settled on a consistent notation (this manual uses at least
+three conflicting styles). Programming languages were clumsy and
+primitive, resources were scarce, and the typical complexity of
+programs was very low. By five years later (roughly three or four
+Moore's-Law doublings) flowcharting was going out of fashion, probably
+for the simple reason that flowcharts were getting too large to draw
+and read!</para>
<para>There are some significant respects in which MAD was actually
rather advanced for its period. The multiline WHENEVER statement
.
</programlisting>
-<para>This statement casues the block of statements which follows
+<para>This statement causes the block of statements which follows
immediately afterwards to be repeatedly executed, each time varying
the value of some variable, until the specified list of values for
that variable is exhausted, or until some specified condition is