Research V3 development

[unix-history] / man / man1 / fc.1

.pa 1
.he 'FC (I)'9/1/72'FC (I)'
.ti 0
NAME		fc -- fortran compiler
.sp
.ti 0
SYNOPSIS	fc\b\b__ [ -c\b\b__ ] sfile\d1\u.f\b\b__ ... ofile\d1\u ...
.sp
.ti 0
DESCRIPTION	fc\b\b__
is the UNIX Fortran compiler.
It accepts three types of arguments:

Arguments whose names end with ".f" are assumed to be
Fortran source program units; they are compiled, and
the object program is left on the file sfile\d1\u.o (i.e.
the file whose name is that of the source with ".o" substituted
for ".f").

Other arguments (except for "-c") are assumed
to be either loader flags, or
object programs, typically produced by an earlier fc\b\b__ run,
or perhaps libraries of Fortran-compatible routines.
These programs, together with the results of any
compilations specified, are loaded (in the order
given) to produce an executable program with name
a.out\b\b\b\b\b_____.

The "-c" argument suppresses the loading phase, as does
any syntax error in any of the routines being compiled.

The following is a list
of differences between fc\b\b__
and ANSI standard Fortran (also see the BUGS section):
.sp
.in +3
.ti -3
1. Arbitrary combination of types is allowed
in expressions.  Not all combinations are expected to
be supported at runtime.
All of the normal
conversions involving integer, real, double
precision and complex are allowed.
.sp
.ti -3
2. The 'standard' implicit statement is recognized.
.sp
.ti -3
3. The types
doublecomplex, logical*1,
integer*2 and real*8 (doubleprecision)
are supported.
.sp
.ti -3
4. &\b_ as the first character of a line
signals a continuation card.
.sp
.ti -3
5. c\b_ as the first character of a line signals a comment.
.sp
.ti -3
6. All keywords are recognized in lower case.
.sp
.ti -3
7. The notion of 'column 7' is not implemented.

.ti -3
8. G-format input is free form--
leading blanks are ignored, the first blank after the start
of the number terminates the field.

.ti -3
9. A comma in any numeric or logical input field terminates
the field.

.ti -4
10. There is no carriage control on output.
.sp
.in -3
In I/O statements, only unit numbers 0-19 are supported.
Unit number nn\b\b__ corresponds to file "fortnn\b\b__;"
(e.g. unit 9 is file "fort09").
For input, the file must exist;
for output, it will be created.

Unit 5 is permanently associated with
the standard input file; unit 6 with the
standard output file.
.sp
.ti 0
FILES		file.f			input file
.nf
a.out			loaded output
f.tmp[123]		temporary (deleted)
/usr/fort/fc[1234]	compilation phases
/usr/lib/fr0.o		runtime startoff
/usr/lib/filib.a	interpreter library
/usr/lib/libf.a		builtin functions, etc.
/usr/lib/liba.a		system library
.fi
.sp
.ti 0
SEE ALSO	ANSI standard
.sp
.ti 0
DIAGNOSTICS	Compile-time diagnostics
are given by number.
If the source code is available, it is
printed with an underline at the current
character pointer.
Errors possible are:

.in +8
.ti -8
1	statement too long
.ti -8
2	syntax error in type statement
.ti -8
3	redeclaration
.ti -8
4	missing ( in array declarator
.ti -8
5	syntax error in dimension statement
.ti -8
6	inappropriate or gratuitous array declarator
.ti -8
7	syntax error in subscript bound
.ti -8
8	illegal character
.ti -8
9	common variable is a parameter or already in common
.ti -8
10	common syntax error
.ti -8
11	subroutine/blockdata/function not first statement
.ti -8
12	subroutine/function syntax error
.ti -8
13	block data syntax error
.ti -8
14	redeclaration in external
.ti -8
15	external syntax error
.ti -8
16	implicit syntax error
.ti -8
17	subscript on non-array
.ti -8
18	incorrect subscript count
.ti -8
19	subscript out of range
.ti -8
20	subscript syntax error
.ti -8
22	DATA syntax error
.ti -8
23	Illegal variable in DATA
.ti -8
23	equivalence inconsistency
.ti -8
24	equivalence syntax error
.ti -8
25	separate common blocks equivalenced
.ti -8
26	common block illegally extended by equivalence
.ti -8
27	common inconsistency created by equivalence
.ti -8
28	DATA table overflow
.ti -8
29	() imbalance in expression
.ti -8
30	expression syntax error
.ti -8
31	illegal variable in equivalence
.ti -8
32	Storage initialized twice by DATA
.ti -8
33	non array/function used with subscripts/arguments
.ti -8
35	goto syntax error
.ti -8
37	illegal return
.ti -8
38	continue, return, stop, call, end, or pause syntax error
.ti -8
39	assign syntax error
.ti -8
40	if syntax error
.ti -8
41	I/O syntax error
.ti -8
42	do or I/O iteration error
.ti -8
43	do end missing
.ti -8
50	illegal statement in block data
.ti -8
51	multiply defined labels
.ti -8
52	undefined label
.ti -8
53	dimension mismatch
.ti -8
54	expression syntax error
.ti -8
55	end of statement in hollerith constant
.ti -8
56	array too large
.ti -8
99	\ eB\ f table overflow
.ti -8
101	unrecognized statement
.ti -8

.ti -8
Runtime diagnostics:
.ti -8

.ti -8
1	invalid log argument
.ti -8
2	bad arg count to amod
.ti -8
3	bad arg count to atan2
.ti -8
4	excessive argument to cabs
.ti -8
5	exp too large in cexp
.ti -8
6	bad arg count to cmplx
.ti -8
7	bad arg count to dim
.ti -8
8	excessive argument to exp
.ti -8
9	bad arg count to idim
.ti -8
10	bad arg count to isign
.ti -8
11	bad arg count to mod
.ti -8
12	bad arg count to sign
.ti -8
13	illegal argument to sqrt
.ti -8
14	assigned/computed goto out of range
.ti -8
15	subscript out of range
.ti -8
16	real**real overflow

.ti -8
100	illegal I/O unit number
.ti -8
101	inconsistent use of I/O unit
.ti -8
102	cannot create output file
.ti -8
103	cannot open input file
.ti -8
104	EOF on input file
.ti -8
105	illegal character in format
.ti -8
106	format does not begin with (
.ti -8
107	no conversion in format but non-empty list
.ti -8
108	excessive parenthesis depth in format
.ti -8
109	illegal format specification
.ti -8
110	illegal character in input field
.ti -8
111	end of format in hollerith specification
.ti -8
999	unimplemented input conversion
.sp
.in -8
.ti 0
BUGS		The following is a list of
those features not yet implemented:
.sp
.br
arithmetic statement functions

backspace, endfile, rewind runtime

binary I/O

no scale factors on input