BSD 1 development
[unix-history] / man6 / px.6
CommitLineData
c2210feb
BJ
1.th PX VI 9/10/77
2.sh NAME
3px \- Pascal interpreter
4.sh SYNOPSIS
5.bd px
6[ obj [ argument ... ] ]
7.sh DESCRIPTION
8.it Px
9interprets the abstract machine code generated by
10.it pi.
11The first argument is the file to be interpreted, and defaults
12to
13\fIobj\fR\|;
14remaining arguments are available to the Pascal program using the
15built-ins
16.it argv
17and
18.it argc.
19.it Px
20is also invoked by
21.it pix
22when running ``load and go''.
23.s3
24If the program terminates abnormally an error message and a
25control flow backtrace are printed.
26The number of statements executed and total execution time
27are printed after normal termination.
28The
29.bd p
30option of
31.it pi
32suppresses all of this except the message indicating the cause
33of abnormal termination.
34.sh FILES
35.dt
36obj default object file
37.br
38pmon.out profile data file
39.sh "SEE ALSO"
40UNIX Pascal User's Manual
41.br
42pi (VI), pix (VI)
43.sh DIAGNOSTICS
44Most run-time error messages are self-explanatory.
45Some of the more unusual ones are:
46.s3
47.lp +6 3
48Reference to an inactive file
49.br
50A file other than
51.it input
52or
53.it output
54was used before a call to
55.it reset
56or
57.it rewrite.
58.s3
59.lp +6 3
60Statement count limit exceeded
61.br
62The limit of 500,000 executed statements
63(which prevents excessive looping or recursion)
64has been exceeded.
65.s3
66.lp +6 3
67Bad data found on integer read
68.lp +6 3
69Bad data found on real read
70.br
71Usually, non-numeric input was found for a number.
72For reals, Pascal requires digits before and after the decimal
73point so that numbers like `.1' or `21.' evoke the second diagnostic.
74.s3
75.lp +6 3
76panic: \fISome message\fP
77.br
78Indicates a internal inconsistency detected in
79.it px
80probably due to a Pascal system bug.
81.i0
82.sh AUTHORS
83Charles B. Haley, William N. Joy, and Ken Thompson
84.sh BUGS
85Calls to the procedures
86.it dispose
87and
88.it linelimit
89are ignored.
90.s3
91Post-mortem traceback is not limited;
92infinite recursion leads to almost infinite traceback.
93.s3
94Because interrupts sometimes find the system in the middle of a
95.bd procedure
96or
97.bd function
98entry or exit,
99the error backtrace on an interrupt is occasionally meaningless.
100The current line is, however, always correct;
101only the call backtrace and the name of the current routine may be lost.