4.3BSD-Reno/share/man/cat1/pi.0

PI(1)			    UNIX Reference Manual			 PI(1)

NNAAMMEE
     ppii - Pascal interpreter code translator

SSYYNNOOPPSSIISS
     ppii [--bbllnnppssttuuwwzz] [--ii _n_a_m_e ...] _n_a_m_e._p

DDEESSCCRRIIPPTTIIOONN
     PPii translates the program in the file _n_a_m_e._p leaving interpreter code in
     the file _o_b_j in the current directory.  The interpreter code can be exe-
     cuted using ppxx.  PPiixx performs the functions of ppii and ppxx for `load and
     go' Pascal.

     The following flags are interpreted by ppii; the associated options can
     also be controlled in comments within the program 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.

     --bb        Block buffer the file _o_u_t_p_u_t.

     --ii        Enable the listing for any specified procedures and functions
	       and while processing any specified iinncclluuddee files.

     --ll        Make a program listing during translation.

     --nn        Begin each listed iinncclluuddee file on a new page with a banner
	       line.

     --pp        Suppress the post-mortem control flow backtrace if an error oc-
	       curs; suppress statement limit counting.

     --ss        Accept standard Pascal only; non-standard constructs cause
	       warning diagnostics.

     --tt        Suppress runtime tests of subrange variables and treat aasssseerrtt
	       statements as comments.

     --uu        Card image mode; only the first 72 characters of input lines
	       are used.

     --ww        Suppress warning diagnostics.

     --zz        Allow execution profiling with ppxxpp 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.

FFIILLEESS
     _f_i_l_e._p		     input file
     _f_i_l_e._i		     include file(s)
     /_u_s_r/_l_i_b/_p_i_2.*_s_t_r_i_n_g_s   text of the error messages
     /_u_s_r/_l_i_b/_h_o_w__p_i*	     basic usage explanation
     _o_b_j		     interpreter code output


SSEEEE AALLSSOO
     _B_e_r_k_e_l_e_y _P_a_s_c_a_l _U_s_e_r'._X_r _s _M_a_n_u_a_l
     pix(1), px(1), pxp(1), pxref(1)

DDIIAAGGNNOOSSTTIICCSS
     For a basic explanation do

	   ppii

     In the diagnostic output of the translator, lines containing syntax er-
     rors 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 pin-
     point 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 transla-
     tor will give a diagnostic and then `QUIT'.

AAUUTTHHOORRSS
     Charles B. Haley, William N. Joy, and Ken Thompson
     Ported to VAX-11 by Peter Kessler

BBUUGGSS
     The keyword ppaacckkeedd 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 pprroocceedduurree or ffuunnccttiioonn rather than
     evoking many diagnostics.

     When iinncclluuddee files are present, diagnostics relating to the last pro-
     cedure in one file may appear after the beginning of the listing of the
     next.

HHIISSTTOORRYY
     PPii appeared in 3 BSD.