master/reconstruct/page003.inc

<!--
        UCSD Pascal System II.0 User Manual
        Copyright (C) 1979 Regents of the University of California

        HTML markup and formatting
        Copyright (C) 2006, 2007, 2010 Peter Miller
-->
<#include reconstruct/page "page003" "3">
textfile.  See Section
<a href="01-03-screen-oriented-editor.html">1.3</a>
for details.  The workfile text (if present)
is read into the editor buffer, otherwise the Editor prompts for a
file.

<a name="filer"></a>
<h3>F(iler</h3>

<p>
&ldquo;F&rdquo; places the user in a level of the system called the Filer.
This section of the system contains commands used primarily for
maintenance of the disk directory.  For more documentation on the
Filer level including commands associated with the &ldquo;getting&rdquo;,
&ldquo;saving&rdquo;, and &ldquo;clearing&rdquo; of the user's workfile see
Section
<a href="01-02-file-handler.html">1.2</a>.

<a name="compile"></a>
<h3>C(omp</h3>

<p>
This command initiates the system compiler to compile the users
workfile.  If there is no work-file currently the user is asked for a
source text file name.  If a syntax error within the source is
detected, the compiler will stop and display the error number and the
surrounding text of the program.  By typing a space, the user can
cause the compiler to continue the compilation.  Typing an &lt;esc&gt; causes
the compiler to abort and return to Command level.  Typing &lsquo;E&rsquo; will
call the editor placing the cursor, if the system editor is the
screen editor, near the offending symbol.  If the compilation is
successful, (<i>i.e.</i> no compilation errors were encountered) a code file
called <tt>SYSTEM.WRK.CODE</tt> is written out onto the user's disk and
becomes part of the workfile.  For more documentation on the use of
the UCSD Pascal compiler see Section
<a href="01-06-pascal-compiler.html">1.6</a>.

<a name="run"></a>
<h3>R(un</h3>

<p>
This command causes the code file associated with the current
workfile to be executed.  If no such code file currently exists, the
compiler is called in the same manner as described in
<a name="compile.56"></a>
<i>C(omp</i> above.
If the
compilation requires linkage to separately compiled code the linker
will automatically be invoked and will assume the use of the file
<tt>*SYSTEM.LIBRARY</tt>.  After a successful compilation, the program is
executed.

<a name="execute"></a>
<h3>X(ecute</h3>

<p>
This command prompts the user for the filename of a previously
compiled codefile.  If the file exists, the code file is executed;
otherwise the message &ldquo;can't find file&rdquo; is returned.  (Note: the
&ldquo;.CODE&rdquo; suffix on such a file is implicit.)
If all code necessary to
execute the codefile has not been linked in, the message &ldquo;must
<a name="link.71"></a>
L(ink
first&rdquo; is returned.  It is convenient to
<a name="execute.74"></a>
X(ecute other programs which
have already been compiled because otherwise the user would have to
enter the Filer,
<a name="get.78"></a>
G(et the file,
<a name="quit.81"></a>
Q(uit the Filer, and then
<a name="run.83"></a>
R(un the program.