PFORT 1L "10 August 1986"
Table of contents
pfort - a FORTRAN code portability verifier.
[-D] [-R] [-S] file
checks FORTRAN code for portability. Also referred to as the Extended
this program takes FORTRAN code appearing in file (one file only,
no wildcards permitted) and checks it
for the presence of non-standard (and hence probably non-portable) code.
The FORTRAN file should use the standard extension .f.
The source file must not contain tab characters or
lower-case letters in FORTRAN keywords.
Options can appear in a options file *.opt, using the same basename
as for the source file. If such a file does not exist, pfort
looks for a file called pfort.opt in the current directory, and then
for a file of that name in the user's home directory.
Output appears in a listing file (with extension .pfl) and
a declaration file (which uses extension .dcl).
This extended Verifier should not be confused with its parent program
of the same name.
There are two sets of options; one set is specified on the command line,
and the other must appear in an options file or the source code.
Three option switches are recognized on the command line:
Write declarations for all undeclared FORTRAN variables
to a declaration (*.dcl) file.
If this option is omitted or all variables are explicitly declared, the
file is not produced.
(Reprocess) Execute even if the listing (*.pfl) file is newer than the
FORTRAN (*.for) file. Normally, processing is terminated in such a case,
just as the COMPILE/LOAD/EXECUTE commands normally do not recompile
If the declare file is produced, SFTRAN3 preprocessor variables
of the form NPRnnn, NXnnnn, N2nnnn,
and N3nnnn (n = digit) will be omitted
from the declarations. This makes the declaration file suitable for
inclusion in the SFTRAN3 source code.
If an options (*.opt) file exists, it should contain only one line,
of the form:
where the options are one- or two-letter codes separated by
commas and any number of spaces.
Such an options line may also be placed directly into the FORTRAN source
Compile program after successful execution.
Do not compile program (default).
Force continued execution after finding illegal statements (default).
Flush to end of program unit after an illegal statement.
Print a listing of each program unit (default).
Do not print a listing.
Perform inter-program-unit checks on this input (default).
To get the maximum benefit from this option, it is advisable
to concatenate all routines for a complete program into a
single file which is then input to PFORT.
Do not perform inter-program-unit checks.
Gather and print cross references for all symbols for each program unit (default).
Do not gather and print cross references.
Print a symbol table for each program unit (default).
Do not print a symbol table.
files required to make pfort
various environment definitions, an appropriate subset of which should be
placed in the user's .cshrc or .profile file
document (1L), drawit(1L), grapht(1L), graph3t(1L), lptops(1L),
piechtt(1L), plot79-intro(1L), plot79(1L), pluto(1L), pretty(1L), rdinfo(1L),
sf3(1L), slides(1L), tekalw(1L), tkvecs(1L), tmacro(1L), world(1L)
The original PFORT Verifier was written by AT&T Bell Laboratories.
By agreement with them, this improved version is known as the
Extended PFORT Verifier.
Nelson H. F. Beebe, Ph.D.
Center for Scientific Computing
South Physics Building
University of Utah
Salt Lake City, UT 84112
Tel: (801) 581-5254
(Manual page by R. P. C. Rodgers, Computer Applications in Laboratory
Medicine Project, UCSF, San Francisco, CA 94143).