1PI(1) General Commands Manual PI(1)
2
6 pi - Pascal interpreter code translator
7
9 pi [ -blnpstuwz ] [ -i name ... ] name.p
10
12 Pi translates the program in the file name.p leaving interpreter code
13 in the file obj in the current directory. The interpreter code can be
14 executed using px. Pix performs the functions of pi and px for `load
15 and go' Pascal.
16 The following flags are interpreted by pi; the associated options can
18 also be controlled in comments within the program as described in the
19 Berkeley Pascal User's Manual.
20 -b Block buffer the file output.
22 -i Enable the listing for any specified procedures and functions and
24 while processing any specified include files.
25 -l Make a program listing during translation.
27 -n Begin each listed include file on a new page with a banner line.
29 -p Suppress the post-mortem control flow backtrace if an error
31 occurs; suppress statement limit counting.
32 -s Accept standard Pascal only; non-standard constructs cause warn‐
34 ing diagnostics.
35 -t Suppress runtime tests of subrange variables and treat assert
37 statements as comments.
38 -u Card image mode; only the first 72 characters of input lines are
40 used.
41 -w Suppress warning diagnostics.
43 -z Allow execution profiling with pxp by generating statement coun‐
45 ters, and arranging for the creation of the profile data file
46 pmon.out when the resulting object is executed.
47
49 file.p input file
50 file.i include file(s)
51 /usr/share/pascal/pi_stringstext of the error messages
52 /usr/share/pascal/how_pi*basic usage explanation
53 obj interpreter code output
54
56 Berkeley Pascal User's Manual
57 pcc(1), pix(1), px(1), pxp(1), pxref(1)
58
60 For a basic explanation do
61 pi
63 In the diagnostic output of the translator, lines containing syntax
65 errors are listed with a flag indicating the point of error. Diagnos‐
66 tic messages indicate the action which the recovery mechanism took in
67 order to be able to continue parsing. Some diagnostics indicate only
68 that the input is `malformed.' This occurs if the recovery can find no
69 simple correction to make the input syntactically valid.
70 Semantic error diagnostics indicate a line in the source text near the
72 point of error. Some errors evoke more than one diagnostic to help
73 pinpoint the error; the follow-up messages begin with an ellipsis
74 `...'.
75 The first character of each error message indicates its class:
77 EFatal error; no code will be generated.
79 eNon-fatal error.
80 wWarning - a potential problem.
81 sNon-standard Pascal construct warning.
82 If a severe error occurs which inhibits further processing, the trans‐
84 lator will give a diagnostic and then `QUIT'.
85
87 Charles B. Haley, William N. Joy, and Ken Thompson
88
90 Formal parameters which are procedures and functions are not supported.
91 The keyword packed and the function dispose are recognized but have no
93 effect.
94 For clarity, semantic errors should be flagged at an appropriate place
96 in the source text, and multiple instances of the `same' semantic error
97 should be summarized at the end of a procedure or function rather than
98 evoking many diagnostics.
99 When include files are present, diagnostics relating to the last proce‐
101 dure in one file may appear after the beginning of the listing of the
102 next.
1033rd Berkeley Distribution PI(1)