1PX(1)                       General Commands Manual                      PX(1)
2
3
4

NAME

6       px - Pascal interpreter
7

SYNOPSIS

9       px [ obj [ argument ... ] ]
10

DESCRIPTION

12       Px  interprets  the  abstract  machine code generated by pi.  The first
13       argument is the file to be interpreted, and defaults to obj;  remaining
14       arguments  are available to the Pascal program using the built-ins argv
15       and argc.  Px is also invoked by pix when running `load and go'.
16
17       If the program terminates abnormally an error  message  and  a  control
18       flow  backtrace  are  printed.   The  number of statements executed and
19       total execution time are  printed  after  normal  termination.   The  p
20       option  of  pi suppresses all of this except the message indicating the
21       cause of abnormal termination.
22

FILES

24       obj                 default object file
25       pmon.out            profile data file
26

SEE ALSO

28       Berkeley Pascal User's Manual
29       pi(1), pix(1)
30

DIAGNOSTICS

32       Most run-time error messages are self-explanatory.  Some  of  the  more
33       unusual ones are:
34
35       Reference to an inactive file
36             A file other than input or output was used before a call to reset
37             or rewrite.
38
39       Statement count limit exceeded
40             The limit of 500,000 executed statements (which  prevents  exces‐
41             sive looping or recursion) has been exceeded.
42
43       Bad data found on integer read
44       Bad data found on real read
45             Usually,  non-numeric  input  was found for a number.  For reals,
46             Pascal requires digits before and after the decimal point so that
47             numbers like `.1' or `21.' evoke the second diagnostic.
48
49       panic: Some message
50             Indicates a internal inconsistency detected in px probably due to
51             a Pascal system bug.  Charles B. Haley, William N. Joy,  and  Ken
52             Thompson
53

BUGS

55       Calls to the procedures dispose and linelimit are ignored.
56
57       Post-mortem  traceback  is  not  limited;  infinite  recursion leads to
58       almost infinite traceback.
59
60       Because interrupts sometimes find the system in the middle of a  proce‐
61       dure  or function entry or exit, the error backtrace on an interrupt is
62       occasionally meaningless.  The current line is,  however,  always  cor‐
63       rect;  only  the call backtrace and the name of the current routine may
64       be lost.
65
66
67
683rd Berkeley Distribution                                                PX(1)