Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

px(1) [bsd man page]

PX(1)							      General Commands Manual							     PX(1)

px - Pascal interpreter SYNOPSIS
px [ obj [ argument ... ] ] DESCRIPTION
Px interprets the abstract machine code generated by pi. The first argument is the file to be interpreted, and defaults to obj; remaining arguments are available to the Pascal program using the built-ins argv and argc. Px is also invoked by pix when running `load and go'. 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 p option of pi suppresses all of this except the message indicating the cause of abnormal termination. FILES
obj default object file pmon.out profile data file SEE ALSO
Berkeley Pascal User's Manual pi(1), pix(1) DIAGNOSTICS
Most run-time error messages are self-explanatory. Some of the more unusual ones are: Reference to an inactive file A file other than input or output was used before a call to reset or rewrite. Statement count limit exceeded The limit of 500,000 executed statements (which prevents excessive looping or recursion) has been exceeded. Bad data found on integer read Bad data found on real read Usually, non-numeric input was found for a number. For reals, Pascal requires digits before and after the decimal point so that num- bers like `.1' or `21.' evoke the second diagnostic. panic: Some message Indicates a internal inconsistency detected in px probably due to a Pascal system bug. Charles B. Haley, William N. Joy, and Ken Thompson BUGS
Calls to the procedures dispose and linelimit are ignored. Post-mortem traceback is not limited; infinite recursion leads to almost infinite traceback. Because interrupts sometimes find the system in the middle of a procedure or 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. 3rd Berkeley Distribution PX(1)

Check Out this Related Man Page

ctags(1)						      General Commands Manual							  ctags(1)

       ctags - create a tags file

       ctags [options] name...

       The command makes a tags file for from the specified C, Pascal and Fortran sources.

       A tags file gives the locations of specified objects (in this case functions and typedefs) in a group of files.	Each line of the tags file
       contains the object name, the file in which it is defined, and an address specification for the object definition.  Functions are  searched
       with a pattern, typedefs with a line number.  Specifiers are given in separate fields on the line, separated by blanks or tabs.

       Using the tags file, can quickly find these objects definitions.

       If  the	-x  flag  is  given,  writes  to standard output a list containing each object name, its line number, the file name in which it is
       defined, and the text of the line.  This list is a simple index which can be printed out as an off-line readable function index.

       -a		   Appends information to an existing tags file.

       -B		   Uses backward search patterns (?...?).

       -F		   Uses forward search patterns (/.../) (default).

       -t		   Creates typedef tags.

       -u		   Updates the specified tags file.  All references to tags are deleted, and the new values  are  appended  to	the  file.
			   Note  that  this  option is implemented in a way which is rather slow.  It is usually faster to simply rebuild the tags

			   The tag main is treated specially in C programs.  The tag formed is created by prepending M to the name  of	the  file,
			   with  a  trailing  .c  removed,  if	any, and leading pathname components also removed.  This makes use of practical in
			   directories with more than one program.

       -v		   Generates an index listing function name, file name, and pages number.  Since the output will be  sorted  into  lexico-
			   graphic order, it may be desired to run the output through sort -f.	For example,
			   ctags -v files | sort -f > index
			   Files  whose  name  ends  in .c or .h are assumed to be C source files and are searched for C routine and macro defini-
			   tions.  Others are first examined to see if they contain any Pascal or Fortran routine definitions; if  not,  they  are
			   processed again looking for C definitions.

       -w		   Suppresses warning diagnostics and generates a listing file.  This list contains each object name, its line number, the
			   file name in which it is defined, and the text of the line, and is identical to the list produced when no  options  are

       -x		   Writes  to  standard  output a list containing each object name, its line number, the file name in whcih it is defined,
			   and the text of the line.

       Recognition of functions, subroutines and procedures for FORTRAN and Pascal do not deal with block structure.  Therefore  you  cannot  have
       two Pascal procedures in different blocks with the same name.

       Does not know about #ifdefs.

       Does  not know about Pascal types.  Relies on the input being well formed to detect typedefs.  Use of -tx shows only the last line of type-

       tags	 output tags file

See Also
       ex(1), vi(1)

Man Page