BSD 4_3_Reno development

[unix-history] / usr / share / man / cat1 / pc.0

PC(1)			    UNIX Reference Manual			 PC(1)

N\bNA\bAM\bME\bE
     p\bpc\bc - Pascal compiler

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     p\bpc\bc [option] [-\b-i\bi _\bn_\ba_\bm_\be ...] _\bn_\ba_\bm_\be ...

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     P\bPc\bc is a Pascal compiler.  If given an argument file ending with ._\bp, it
     will compile the file and load it into an executable file called, by de-
     fault, _\ba._\bo_\bu_\bt.

     A program may be separated into more than one ._\bp file.  P\bPc\bc will compile a
     number of argument ._\bp files into object files (with the extension ._\bo in
     place of ._\bp).  Object files may then be loaded into an executable _\ba._\bo_\bu_\bt
     file.  Exactly one object file must supply a _\bp_\br_\bo_\bg_\br_\ba_\bm statement to suc-
     cessfully create an executable a.out file.  The rest of the files must
     consist only of declarations which logically nest within the program.
     References to objects shared between separately compiled files are al-
     lowed if the objects are declared in i\bin\bnc\bcl\blu\bud\bde\bed\bd header files, whose names
     must end with ._\bh.	Header files may only be included at the outermost
     level, and thus declare only globally available objects.  To allow
     f\bfu\bun\bnc\bct\bti\bio\bon\bns and p\bpr\bro\boc\bce\bed\bdu\bur\bre\bes to be declared, an e\bex\bxt\bte\ber\brn\bna\bal\bl directive has been
     added, whose use is similar to the f\bfo\bor\brw\bwa\bar\brd\bd directive but restricted to
     appear only in ._\bh files.  F\bFu\bun\bnc\bct\bti\bio\bon\bn and p\bpr\bro\boc\bce\bed\bdu\bur\bre\be bodies may not appear in
     ._\bh files.	A binding phase of the compiler checks that declarations are
     used consistently, to enforce the type checking rules of Pascal.

     Object files created by other language processors may be loaded together
     with object files created by p\bpc\bc.  The f\bfu\bun\bnc\bct\bti\bio\bon\bns and p\bpr\bro\boc\bce\bed\bdu\bur\bre\bes they
     define must have been declared in ._\bh files included by all the ._\bp files
     which call those routines.  Calling conventions are as in C, with v\bva\bar\br
     parameters passed by address.

     See the Berkeley Pascal User's Manual for details.

     The following options have the same meaning as in cc(1) and f77(1).  See
     ld(1) for load-time options.

     -\b-c\bc        Suppress loading and produce `.o' file(s) from source file(s).

     -\b-g\bg        Have the compiler produce additional symbol table information
	       for dbx(1).

     -\b-w\bw        Suppress warning messages.

     -\b-p\bp        Prepare object files for profiling, see prof(1).

     -\b-O\bO        Invoke an object-code improver.

     -\b-S\bS        Compile the named program, and leave the assembler-language
	       output on the corresponding file suffixed `.s'.	(No `.o' is
	       created.).

     -\b-o\bo _\bo_\bu_\bt_\bp_\bu_\bt
	       Name the final output file _\bo_\bu_\bt_\bp_\bu_\bt instead of _\ba._\bo_\bu_\bt.

     The following options are peculiar to p\bpc\bc.

     -\b-C\bC        Compile code to perform runtime checks, verify a\bas\bss\bse\ber\brt\bt calls,
	       and initialize all variables to zero as in p\bpi\bi.

     -\b-b\bb        Block buffer the file _\bo_\bu_\bt_\bp_\bu_\bt.

     -\b-i\bi        Produce a listing for the specified procedures, functions and
	       _\bi_\bn_\bc_\bl_\bu_\bd_\be files.
     -\b-l\bl        Make a program listing during translation.

     -\b-s\bs        Accept standard Pascal only; non-standard constructs cause
	       warning diagnostics.

     -\b-t\bt _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by
	       Use the given _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by for compiler temporary files.

     -\b-z\bz        Allow execution profiling with p\bpx\bxp\bp by generating statement
	       counters, and arranging for the creation of the profile data
	       file _\bp_\bm_\bo_\bn._\bo_\bu_\bt when the resulting object is executed.

     Other arguments are taken to be loader option arguments, perhaps li-
     braries of p\bpc\bc compatible routines.  Certain flags can also be controlled
     in comments within the program as described in the _\bB_\be_\br_\bk_\be_\bl_\be_\by _\bP_\ba_\bs_\bc_\ba_\bl _\bU_\bs_\be_\br'_\bs
     _\bM_\ba_\bn_\bu_\ba_\bl.

F\bFI\bIL\bLE\bES\bS
     _\bf_\bi_\bl_\be._\bp		     pascal source files
     /_\bu_\bs_\br/_\bl_\bi_\bb/_\bp_\bc_\b0	     compiler
     /_\bl_\bi_\bb/_\bf_\b1		     code generator
     /_\bu_\bs_\br/_\bl_\bi_\bb/_\bp_\bc_\b2	     runtime integrator (inline expander)
     /_\bl_\bi_\bb/_\bc_\b2		     peephole optimizer
     /_\bu_\bs_\br/_\bl_\bi_\bb/_\bp_\bc_\b3	     separate compilation consistency checker
     /_\bu_\bs_\br/_\bl_\bi_\bb/_\bp_\bc_\b2.*_\bs_\bt_\br_\bi_\bn_\bg_\bs   text of the error messages
     /_\bu_\bs_\br/_\bl_\bi_\bb/_\bh_\bo_\bw__\bp_\bc	     basic usage explanation
     /_\bu_\bs_\br/_\bl_\bi_\bb/_\bl_\bi_\bb_\bp_\bc._\ba	     intrinsic functions and I/O library
     /_\bu_\bs_\br/_\bl_\bi_\bb/_\bl_\bi_\bb_\bm._\ba	     math library
     /_\bl_\bi_\bb/_\bl_\bi_\bb_\bc._\ba	     standard library, see intro(3)


S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     _\bB_\be_\br_\bk_\be_\bl_\be_\by _\bP_\ba_\bs_\bc_\ba_\bl _\bU_\bs_\be_\br'_\bs _\bM_\ba_\bn_\bu_\ba_\bl
     pi(1), pxp(1), pxref(1),

H\bHI\bIS\bST\bTO\bOR\bRY\bY
     P\bPc\bc appeared in 4.0 BSD.

D\bDI\bIA\bAG\bGN\bNO\bOS\bST\bTI\bIC\bCS\bS
     For a basic explanation do

	   p\bpc\bc

     See pi(1).  for an explanation of the error message format.  Internal er-
     rors cause messages containing the word SNARK.

A\bAU\bUT\bTH\bHO\bOR\bRS\bS
     Charles B. Haley, William N. Joy, and Ken Thompson
     Retargetted to the second pass of the portable _\bC compiler by Peter
     Kessler
     Runtime library and inline optimizer by M. Kirk McKusick
     Separate compilation consistency checking by Louise Madrid

B\bBU\bUG\bGS\bS
     The keyword p\bpa\bac\bck\bke\bed\bd is recognized but has no effect.

     The binder is not as strict as described here, with regard to the rules
     about external declarations only in `.h' files and including `.h' files
     only at the outermost level.  It will be made to perform these checks in
     its next incarnation, so users are warned not to be sloppy.

     The -\b-z\bz flag doesn't work for separately compiled files.

     Because the -\b-s\bs option is usurped by the compiler, it is not possible to
     pass the strip option to the loader.  Thus programs which are to be
     stripped, must be run through strip(1) after they are compiled.