called floating point numbers.] <indexterm><primary>Constants,
Floating Point</primary></indexterm> Numbers are assumed to be in the
floating-point mode unless otherwise declared, as in the INTEGER
-statement in the example. The WHENEVER statement above is to be
+statement in the example. <indexterm><primary>INTEGER
+Statement</primary></indexterm> The WHENEVER statement above is to be
interpreted in the sense: Whenever the following condition (in this
case Z < a<subscript>j</subscript>) is satisfied, do the specified
action (Z = a<subscript>j</subscript>), otherwise just go on.</para>
<sect3><title>Integer Constants</title>
<indexterm><primary>Constants, Integer</primary></indexterm>
+<indexterm><primary>Integer Constants</primary></indexterm>
<para>Integer constants contain from 2 to 10 decimal digits. The
decimal point is assumed to be immediately to the right of the
D are integers, the result is again an integer; e.g., the "fractional
part" of the true quotient is truncated (not rounded). For example,
if Z5 = 7, and D = 3, the Z5 = D will have the value 2.
-<indexterm><primary>Division</primary></indexterm> </para></listitem>
+<indexterm><primary>Division</primary></indexterm>
+<indexterm><primary>Integer Division</primary></indexterm></para></listitem>
<!-- beginpage II.4 -->
<listitem><para>Exponentiation, written as ".P.", e.g., Z5.P.D, and
greater than 134,217,728 (i.e. 2<superscript>27</superscript>) then an
improper conversion will take place.</para>
+<indexterm><primary>Integer Conversions</primary></indexterm>
+
<para>In some cases, however, the user must understand the sequence in
which the conversions will be made. Consider the expression</para>
but in this case the conversation of the integer is unnecessary, thus
speeding up the computation.</para>
+<indexterm><primary>Integer Conversions</primary></indexterm>
+
<para>When a floating point number is to be converted to an integer,
it is first expressed as a number with both an integer part and a
fractional part, and then the fractional part is truncated. Thus, the
<!-- beginpage II.23 -->
<sect2><title>Input-Output Statements</title>
+<indexterm><primary>Input-Output Statements</primary></indexterm>
+
<note><para> The Retrocomputing Museum implementation does not
implement TAPE and DRUM statements.</para></note>
+<indexterm><primary>Input-Output List</primary></indexterm>
+
<para>In this section the follwing definition the following
definitions will hold. &scriptF; is the location of a format
specification vector (see <xref linkend='format_specs'/>) which must
</sect3>
<sect3><title>Relationship between the List and the Specification</title>
+<indexterm><primary>Input-Output List</primary></indexterm>
+
<para>The "list" consists of a set of names of variables to or from
which information is to flow. Except for Hollerith strings imbedded
in the format specification itself (see <xref
<indexterm><primary>Function Arguments</primary><see>Arguments of Functions</see></indexterm>
<indexterm><primary>Function Statement</primary><see>Execute Statement</see></indexterm>
<indexterm><primary>Function Value</primary><see>Value of a Function</see></indexterm>
-<indexterm><primary>Hierarchy of Parrentheses</primary><see>Parentheses</see></indexterm>
+<indexterm><primary>Hierarchy of Parentheses</primary><see>Parentheses</see></indexterm>
+<indexterm><primary>Individual Variables</primary><see>Single Variables</see></indexterm>
+<indexterm><primary>Input-Output Blocks</primary><see>Blocks, Input-Output</see></indexterm>
<index/>