ferror.gml

开放源码的编译器open watcom 1.6.0版的源代码

.pc
The variable %s1 is used to express the array elements in the DATA
statement but the variable is not used as an implied DO variable.
.note DA-04
.bi %s1 in blank COMMON block cannot be initialized
.pc
A blank or unnamed COMMON block is a COMMON statement with the block
name omitted.
The entries in blank COMMON blocks cannot be initialized using DATA
statements.
.note DA-05
.bi data initialization with hexadecimal constant is not FORTRAN 77 standard
.pc
Data initialization with hexadecimal constants is an extension to the
FORTRAN 77 language.
.note DA-06
.bi cannot initialize %s1 %s2
.pc
Symbol %s2 was used as a %s1.
It is illegal for such a symbol to be initialized in a DATA statement.
The DATA statement can only be used to initialize variables, arrays,
array elements, and substrings.
.note DA-07
.bi data initialization in %s1 statement is not FORTRAN 77 standard
.pc
Data initialization in type specification statements is an extension
to the FORTRAN 77 language.
These include: CHARACTER, COMPLEX, DOUBLE PRECISION, INTEGER,
LOGICAL, and REAL.
.note DA-09
.bi not enough constants for list of variables
.pc
There are not enough constants specified to initialize all of the
names listed in the DATA statement.
.note DA-11
.bi too many constants for list of variables
.pc
There are too many constants specified to initialize the names listed
in the DATA statement.
.note DA-13
.bi cannot initialize %s1 variable with %s2 constant
.pc
The constant of type %s2 cannot be used to initialize a variable of
type %s1.
.note DA-14
.bi entity can only be initialized once during data initialization
.pc
An attempt has been made to initialize an entity more than once in
DATA statements.
.endnote
.begnote
:DTHD.Dimensioned Variables
:DDHD.~b
.note DM-01
.bi using %s1 incorrectly in dimension expression
.pc
The name used as a dimension declarator has been previously declared
as type %s1 and cannot be used as a dimension declarator. A dimension
declarator must be an integer expression.
.note DM-02
.bi allocatable array is not FORTRAN 77 standard
.pc
Allocatable arrays are extensions to the FORTRAN 77 standard.
.note DM-03
.bi array or array element (possibly substrung) associated with %s1 too small
.pc
The dummy argument, array %s1, is defined to be larger than the size
of the actual argument.
.endnote
.begnote
:DTHD.DO-loops
:DDHD.~b
.note DO-01
.bi statement number %d1 already defined in line %d2 - DO loop is backwards
.pc
The statement number to indicate the end of the DO control structure
has been used previously in the program unit and cannot be used to
terminate the DO loop.
The terminal statement named in the DO statement must follow the DO
statement.
.note DO-02
.bi %s1 statement not allowed at termination of DO range
.pc
A non-executable statement cannot be used as the terminal statement
of a DO loop.
These statements include: all declarative statements,
ADMIT, AT END, BLOCK DATA, CASE, DO, ELSE, ELSE IF, END, END AT END,
END BLOCK, END GUESS, END IF, END LOOP, END SELECT, END WHILE, ENTRY,
FORMAT, FUNCTION, assigned GO TO, unconditional GO TO, GUESS,
arithmetic and block IF, LOOP, OTHERWISE, PROGRAM, RETURN, SAVE,
SELECT, STOP, SUBROUTINE, UNTIL, and WHILE.
.note DO-03
.bi improper nesting of DO loop
.pc
A nested DO loop has not been properly terminated before the
termination of the outer DO loop.
.note DO-04
.bi ENDDO cannot terminate DO loop with statement label
.pc
The ENDDO statement can only terminate a DO loop in which no
statement label was specified in the defining DO statement.
.note DO-05
.bi this DO loop form is not FORTRAN 77 standard
.pc
As an extension to FORTRAN 77, the following forms of the DO loop are
also supported.
.autonote
.note
A DO loop with no statement label specified in the defining DO
statement.
.note
The DO WHILE form of the DO statement.
.endnote
.note DO-06
.bi expecting comma or DO variable
.pc
The item following the DO keyword and the terminal statement-label
(if present) must be either a comma or a DO variable.
A DO variable is an integer, real or double precision variable name.
The DO statement syntax is as follows:
.millust begin
DO <tsl> <,> DO-var = ex, ex <, ex>
.millust end
.note DO-07
.bi DO variable cannot be redefined while DO loop is active
.pc
The DO variable named in the DO statement cannot have its value
altered by a statement in the DO loop structure.
.note DO-08
.bi incrementation parameter for DO-loop cannot be zero
.pc
The third expression in the DO statement cannot be zero.
This expression indicates the increment to the DO variable each
iteration of the DO loop.
If the increment expression is not specified a value of 1 is assumed.
.endnote
.begnote
:DTHD.Equivalence and/or Common
:DDHD.~b
.note EC-01
.bi equivalencing %s1 has caused extension of COMMON block %s2 to the left
.pc
The name %s1 has been equivalenced to a name in the COMMON block %s2.
This relationship has caused the storage of the COMMON block to be
extended to the left.
FORTRAN 77 does not allow a COMMON block to be extended in this way.
.note EC-02
.bi %s1 and %s2 in COMMON are equivalenced to each other
.pc
The names %s1 and %s2 appear in different COMMON blocks and each
occupies its own piece of storage and therefore cannot be
equivalenced.
.endnote
.begnote
:DTHD.END Statement
:DDHD.~b
.note EN-01
.bi missing END statement
.pc
The END statement for a PROGRAM, SUBROUTINE, FUNCTION or BLOCK DATA subprogram
was not found before the next subprogram or the end of the source input
stream.
.endnote
.begnote
:DTHD.Equal Sign
:DDHD.~b
.note EQ-01
.bi target of assignment is illegal
.pc
The target of an assignment statement, an input/output status specifier
in an input/output statement, or an inquiry specifier in an INQUIRE
statement, is illegal.
The target in any of the above cases must be a variable name, array element,
or a substring name.
.note EQ-02
.bi cannot assign value to %s1
.pc
An attempt has been made to assign a value to a symbol with class %s1.
For example, an array name cannot be the target of an assignment
statement.
This error may also be issued when an illegal target is used for the
input/output status specifier in an input/output statement or an inquiry
specifier in an INQUIRE statement.
.note EQ-03
.bi illegal use of equal sign
.pc
An equal sign has been found in the statement but the statement is
not an assignment statement.
.note EQ-04
.bi multiple assignment is not FORTRAN 77 standard
.pc
More than one equal sign has been found in the assignment statement.
.note EQ-05
.bi expecting equals sign
.pc
The equal sign is missing or misplaced.
The PARAMETER statement uses an equal sign to equate a symbolic name
to the value of a constant expression.
The I/O statements use an equal sign to equate the appropriate values
to the various specifiers.
The DO statement uses an equal sign to assign the initial value to
the DO variable.
.endnote
.begnote
:DTHD.Equivalenced Variables
:DDHD.~b
.note EV-01
.bi %s1 has been equivalenced to 2 different relative positions
.pc
The storage unit referenced by %s1 has been equivalenced to two
different storage units starting in two different places.
One name cannot be associated to two different values at the same
time.
.note EV-02
.bi EQUIVALENCE list must contain at least 2 names
.pc
The list of names to make a storage unit equivalent to several names
must contain at least two names.
.note EV-03
.bi %s1 incorrectly subscripted in %s2 statement
.pc
The name %s1 has been incorrectly subscripted in a %s2 statement.
.note EV-04
.bi incorrect substring of %s1 in %s2 statement
.pc
An attempt has been made to incorrectly substring %s1 in a %s2
statement.
For example, if a CHARACTER variable was declared to be of length 4
then (2:5) would be an invalid substring expression.
.note EV-05
.bi equivalencing CHARACTER and non-CHARACTER data is not FORTRAN 77 standard
.pc
Equivalencing numeric and character data is an extension to the
FORTRAN 77 language.
.note EV-06
.bi attempt to substring %s1 in EQUIVALENCE statement but type is %s2
.pc
An attempt has been made to substring the symbolic name %s1 in an
EQUIVALENCE statement but the type of the name is %s2 and should be
of type CHARACTER.
.endnote
.begnote
:DTHD.Exponentiation
:DDHD.~b
.note EX-01
.bi zero**J where J <= 0 is not allowed
.pc
Zero cannot be raised to a power less than or equal to zero.
.note EX-02
.bi X**Y where X < 0.0, Y is not of type INTEGER, is not allowed
.pc
When X is less than zero, Y may only be of type INTEGER.
.note EX-03
.bi (0,0)**Y where Y is not real is not allowed
.pc
In complex exponentiation, when the base is zero, the exponent may only be a
real number or a complex number whose imaginary part is zero.
.endnote
.begnote
:DTHD.ENTRY Statement
:DDHD.~b
.note EY-01
.bi type of entry %s1 does not match type of function %s2
.pc
If the type of a function is CHARACTER or a user-defined STRUCTURE, then the
type of all entry names must match the type of the function name.
.note EY-02
.bi ENTRY statement not allowed within structured control blocks
.pc
FORTRAN 77 does not allow an ENTRY statement to appear between the
start and end of a control structure.
.note EY-03
.bi size of entry %s1 does not match size of function %s2
.pc
The name %s1 found in an ENTRY statement must be declared to be the
same size as that of the function name.
If the name of the function or the name of any entry point has a
length specification of (*), then all such entries must have a length
specification of (*) otherwise they must all have a length
specification of the same integer value.
.endnote
.begnote
:DTHD.Format
:DDHD.~b
.note FM-01
.bi missing delimiter in format string, comma assumed
.pc
The omission of a comma between the descriptors listed in a format
string is an extension to the FORTRAN 77 language.
Care should be taken when omitting the comma since the assumed
separation may not occur in the intended place.
.note FM-02
.bi missing or invalid constant
.pc
An unsigned integer constant was expected with the indicated edit
descriptor but was not correctly placed or was missing.
.note FM-03
.bi Ew.dDe format code is not FORTRAN 77 standard
.pc
The edit descriptor Ew.dDe is an extension to the FORTRAN 77
language.
.note FM-04
.bi missing decimal point
.pc
The indicated edit descriptor must have a decimal point and an
integer to indicate the number of decimal positions.
These edit descriptors include: F, E, D and G.
.note FM-05
.bi missing or invalid edit descriptor in format string
.pc
In the format string, two delimiters were found in succession with no
valid descriptor in between.
.note FM-06
.bi unrecognizable edit descriptor in format string
.pc
An edit descriptor has been found in the format string that is not a
valid code.
Valid codes are: apostrophe ('), I, F, E, D, G, L, A, Z, H, T, TL,
TR, X, /, :, S, SP, SS, P, BN, B, $, and \.
.note FM-07
.bi invalid repeat specification
.pc
The indicated repeatable edit descriptor is invalid.
The forms of repeatable edit descriptors are:
Iw, Iw.m, Fw.d, Ew.d, Ew.dEe, Dw.d, Gw.d, Gw.dEe, Lw, A, Aw, Ew.dDe,
and Zw where w and e are positive unsigned integer constants, and d
and m are unsigned integer constants.
.note FM-08
.bi $ or \ format code is not FORTRAN 77 standard
.pc
The non-repeatable edit descriptors $ and \ are extensions to the
FORTRAN 77 language.
.note FM-09
.bi invalid field modifier
.pc
The indicated edit descriptor for a field is incorrect.
Consult the Language Reference for the correct form of the edit descriptor.
.note FM-10
.bi expecting end of FORMAT statement but found more text
.pc
The right parenthesis was encountered in the FORMAT statement to
terminate the statement and more text was found on the line.
.note FM-11
.bi repeat specification not allowed for this format code
.pc
A repeat specification was found in front of a format code that is a
nonrepeatable edit descriptor.
These include: apostrophe, H, T, TL, TR, X, /, :, S, SP, SS, P, BN,
BZ, $,and \.
.note FM-12
.bi no statement number on FORMAT statement
.pc
The FORMAT statement must have a statement label.
This statement number is used by I/O statements to reference the
FORMAT statement.
.note FM-13
.bi no closing quote on apostrophe edit descriptor
.pc
The closing quote of an apostrophe edit descriptor was not found.
.note FM-14
.bi field count greater than 256 is invalid
.pc