[unix-history] / man / px.u

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