pi \- Pascal interpreter code translator
translates the program in the file
leaving interpreter code in the file
in the current directory.
The interpreter code can be executed using
performs the functions of
for `load and go' Pascal.
The following flags are interpreted by
the associated options can also be controlled in comments within the program
.I "Berkeley Pascal User's Manual."
any specified procedures and functions and while processing any specified
Make a program listing during translation.
file on a new page with a banner line.
Suppress the post-mortem control flow backtrace
suppress statement limit counting.
Accept standard Pascal only;
non-standard constructs cause warning diagnostics.
Suppress runtime tests of subrange variables and treat
only the first 72 characters of input lines are used.
Suppress warning diagnostics.
Allow execution profiling with
by generating statement counters, and arranging for the
creation of the profile data file
when the resulting object is executed.
file.i \fBinclude\fR file(s)
/usr/lib/pi_strings text of the error messages
/usr/lib/how_pi* basic usage explanation
obj interpreter code output
Berkeley Pascal User's Manual
For a basic explanation do
In the diagnostic output of the translator,
lines containing syntax errors are listed with a flag indicating the
Diagnostic messages indicate the action which the recovery mechanism
took in order to be able to continue parsing.
Some diagnostics indicate only that the input is `malformed.'
This occurs if the recovery can find no simple correction to make the input
Semantic error diagnostics indicate a line in the source text near the
Some errors evoke more than one diagnostic to help pinpoint the error;
the follow-up messages begin with an ellipsis `...'.
The first character of each error message indicates its class:
E Fatal error; no code will be generated.
w Warning \- a potential problem.
s Non-standard Pascal construct warning.
If a severe error occurs which inhibits further processing,
the translator will give a diagnostic and then `QUIT'.
Charles B. Haley, William N. Joy, and Ken Thompson
Ported to VAX-11 by Peter Kessler
Formal parameters which are procedures and functions are not supported.
are recognized but have no effect.
semantic errors should be flagged at an appropriate place in the source text,
and multiple instances of the `same' semantic error should be summarized
rather than evoking many diagnostics.
diagnostics relating to the last procedure in one file may appear after the
beginning of the listing of the next.