<!ENTITY truthtable SYSTEM "../madhouse/truthtable.mad">
<!ENTITY simpsfunc SYSTEM "../madhouse/simpsfunc.mad">
<!ENTITY simpsmain SYSTEM "../madhouse/simpsmain.mad">
+<!ENTITY findroot SYSTEM "../madhouse/findroot.mad">
<!ENTITY scope1 SYSTEM "scope1.xml">
<!ENTITY scope2 SYSTEM "scope2.xml">
<!ENTITY scope3 SYSTEM "scope3.xml">
<para>The PIC diagrams preserve the logic of the original hand-drawn
ones, but are not exact geometrical duplicates. The proportions of
-the flowchart elements are slightly different.</para>
+the flowchart elements are slightly different. One detail we have not
+preserved is that in Chapter 3, PRINT-statement boxes are left-right
+reversed from their orientation in Chapter 2 (this shows in the
+bottom curve.) Where the original used monospaced fonts and
+hand-drawn Greek characters, PIC and EQN give us typeset formulas
+quite a bit better looking.</para>
<para>In the original, sections were numbered only down to three
levels deep. No per-chapter tables of contents were present.</para>
</programlisting>
<!-- beginpage -->
+</sect2>
+<sect2><title>Example 4</title>
+
+<!-- FIXME -->
+
+
+<!-- beginpage -->
+<para><emphasis>Flow diagram:</emphasis></para>
+
+<mediaobject>
+ <imageobject>
+ <imagedata fileref='fig10.png'/>
+ </imageobject>
+</mediaobject>
+<!-- beginpage -->
+
+<para><emphasis>Program:</emphasis>It is assumed here that f
+(referred to as F. in the program) will be defined as an internal
+function.)</para>
+
+<para><emphasis>Definition:</emphasis> SIGN.(Z) = Z/|Z|</para>
+
+<note><para>A sample F. is actually specified in the listing.
+Specifying F this way makes more sense if one recalls that MAD
+programs were punched-card decks. An internal function definition was
+typically a single card that could be slipped anywhere into the
+program deck.</para></note>
+
+<!-- pagebreak after the VECTOR VALUES ABEPS line -->
+<programlisting>
+&findroot;
+*DATA
+ 1. 2. .01
+</programlisting>
+<!-- pagebreak -->
+
</sect2>
</sect1>
</chapter>