4.3BSD-UWisc/man/cat1/pi.1
PI(1) UNIX Programmer's Manual PI(1)
NAME
pi - Pascal interpreter code translator
SYNOPSIS
pi [ option ] [ -i name ... ] name.p
DESCRIPTION
_P_i translates the program in the file _n_a_m_e._p leaving inter-
preter code in the file _o_b_j in the current directory. The
interpreter code can be executed using _p_x. _P_i_x performs the
functions of _p_i and _p_x for `load and go' Pascal.
The following flags are interpreted by _p_i; the associated
options can also be controlled in comments within the pro-
gram as described in the _B_e_r_k_e_l_e_y _P_a_s_c_a_l _U_s_e_r'_s _M_a_n_u_a_l.
-b Block buffer the file _o_u_t_p_u_t.
-i Enable the listing for any specified procedures and
functions and while processing any specified include
files.
-l Make a program listing during translation.
-n Begin each listed include file on a new page with a
banner line.
-p Suppress the post-mortem control flow backtrace if an
error occurs; suppress statement limit counting.
-s Accept standard Pascal only; non-standard constructs
cause warning diagnostics.
-t Suppress runtime tests of subrange variables and treat
assert statements as comments.
-u Card image mode; only the first 72 characters of input
lines are used.
-w Suppress warning diagnostics.
-z Allow execution profiling with _p_x_p by generating
statement counters, and arranging for the creation of
the profile data file _p_m_o_n._o_u_t when the resulting
object is executed.
FILES
file.p input file
file.i include file(s)
/usr/lib/pi2.*strings text of the error messages
/usr/lib/how_pi* basic usage explanation
obj interpreter code output
Printed 12/27/86 April 29, 1985 1
PI(1) UNIX Programmer's Manual PI(1)
SEE ALSO
Berkeley Pascal User's Manual
pix(1), px(1), pxp(1), pxref(1)
DIAGNOSTICS
For a basic explanation do
pi
In the diagnostic output of the translator, lines containing
syntax errors are listed with a flag indicating the point of
error. 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 syntactically valid.
Semantic error diagnostics indicate a line in the source
text near the point of error. 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.
e Non-fatal error.
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'.
AUTHORS
Charles B. Haley, William N. Joy, and Ken Thompson
Ported to VAX-11 by Peter Kessler
BUGS
The keyword packed is recognized but has no effect.
For clarity, semantic errors should be flagged at an
appropriate place in the source text, and multiple instances
of the `same' semantic error should be summarized at the end
of a procedure or function rather than evoking many diagnos-
tics.
When include files are present, diagnostics relating to the
last procedure in one file may appear after the beginning of
the listing of the next.
Printed 12/27/86 April 29, 1985 2