ferror.gml

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

.errhead Subprogram Arguments
.errnote AR-01 invalid number of arguments to intrinsic function %s1
.pc
The number of actual arguments specified in the argument list for the
intrinsic function %s1 does not agree with the dummy argument list.
Consult the Language Reference for information on intrinsic functions and
their arguments.
.errnote AR-02 dummy argument %s1 appears more than once
.pc
The same dummy argument %s1 is named more than once in the dummy
argument list.
.errnote AR-12 dummy argument %s1 must not appear before definition of ENTRY %s2
.pc
The dummy argument %s1 has appeared in an executable statement before
its appearance in the definition of %s2 in an ENTRY statement.
This is illegal.
.errtail
.errhead Block Data Subprograms
.errnote BD-01 %s1 was initialized in a block data subprogram but is not in COMMON
.pc
The variable or array element, %s1, was initialized in a BLOCK DATA
subprogram but was not specified in a named COMMON block.
.errnote BD-02 %s1 statement is not permitted in a BLOCK DATA subprogram
.pc
The statement, %s1, is not allowed in a BLOCK DATA subprogram.
The only statements which are allowed to appear are:
IMPLICIT, PARAMETER, DIMENSION, COMMON, SAVE, EQUIVALENCE, DATA, END,
and type statements.
.errtail
.errhead Source Format and Contents
.errnote CC-01 invalid character encountered in source input
.pc
The indicated statement contains an invalid character.
Valid characters are: letters, digits, $, *, ., +, &minus., /, :, =, (, ),
!, %,  ', and ,(comma).
Any character may be used inside a character or hollerith string.
.errnote CC-02 invalid character in statement number columns
.pc
A column in columns 1 to 5 of the indicated statement contains a
non-digit character.
Columns 1 to 5 contain the statement number label.
It is made up of digits from 0 to 9 and is greater than 0 and less
than or equal to 99999.
.errnote CC-03 character in continuation column, but no statement to continue
.pc
The character in column 6 indicates that this line is a continuation
of the previous statement but there is no previous statement to
continue.
.errnote CC-04 character encountered is not FORTRAN 77 standard
.pc
A non-standard character was encountered in the source input stream.
This is most likely caused by the use of lower case letters.
.errnote CC-05 columns 1-5 in a continuation line must be blank
.pc
When column 6 is marked as a continuation statement to the previous
line, columns 1 to 5 must be left blank.
.errnote CC-06 more than 19 continuation lines is not FORTRAN 77 standard
.pc
More than 19 continuation lines is an extension to the FORTRAN 77 language.
.errnote CC-07 end-of-line comment is not FORTRAN 77 standard
.pc
End-of-line comments are an extension to the FORTRAN 77 language.
End-of-line comments start with the exclamation mark (!) character.
.errnote CC-08 D in column 1 is not FORTRAN 77 standard
.pc
A "D" in column 1 signifies a debug statement that is compiled
when the "__debug__" macro symbol is defined.
If the "__debug__" macro symbol is not defined, the statement is ignored.
The "c$define" compiler directive or the "define" compiler option can be
used to define the "__debug__" macro symbol.
.errnote CC-09 too many continuation lines
.pc
The limit on the number of continuation lines has been reached.
This limit depends on the size of each continuation line.
A minimum of 61 continuation lines is permitted.
If the "xline" option is used, a minimum of 31 continuation lines is
permitted.
.errtail
.errhead COMMON Blocks
.errnote CM-01 %s1 already in COMMON
.pc
The variable or array name, %s1, has already been specified in this or
another COMMON block.
.errnote CM-02 initializing %s1 in COMMON outside of block data subprogram is not FORTRAN 77 standard
.pc
The symbol %s1, in a named COMMON block, has been initialized outside of a
block data subprogram.
This is an extension to the FORTRAN 77 language.
.errnote CM-03 character and non-character data in COMMON is not FORTRAN 77 standard
.pc
The FORTRAN 77 standard specifies that a COMMON block cannot contain
both numeric and character data.
Allowing COMMON blocks to contain both numeric and character data is an
extension to the FORTRAN 77 standard.
.errnote CM-04 COMMON block %s1 has been defined with a different size
.pc
The COMMON block %s1 has been defined with a different size in another
subprogram.
A named COMMON block must define the same amount of storage units
where ever named.
.errnote CM-05 named COMMON block %s1 appears in more than one BLOCK DATA subprogram
.pc
The named COMMON block, %s1, may not appear in more than one BLOCK
DATA subprogram.
.errnote CM-06 blank COMMON block has been defined with a different size
.pc
The blank COMMON block has been defined with a different size in
another subprogram.
This is legal but a warning message is issued.
.errtail
.errhead Constants
.errnote CN-01 DOUBLE PRECISION COMPLEX constants are not FORTRAN 77 standard
.pc
Double precision complex numbers are an extension to the FORTRAN 77
language.
The indicated number is a complex number and at least one of the
parts, real or imaginary, is a double precision constant.
Both real and imaginary parts will be double precision.
.errnote CN-02 invalid floating-point constant %s1
.pc
The floating-point constant %s1 is invalid.
Refer to the chapter entitled "Names, Data Types and Constants"
in the Language Reference.
.errnote CN-03 zero length character constants are not allowed
.pc
FORTRAN 77 does not allow character constants of length 0 (i.e., an
empty string).
.errnote CN-04 invalid hexadecimal/octal constant
.pc
An invalid hexadecimal or octal constant was specified.
Hexadecimal constants can only contain digits or the letters 'a' through
'f' and 'A' through 'F'.
Octal constants can only contain the digits '0' through '7'.
.errnote CN-05 hexadecimal/octal constant is not FORTRAN 77 standard
.pc
Hexadecimal and octal constants are extensions to the FORTRAN 77 standard.
.errtail
.errhead Compiler Options
.errnote CO-01 %s1 is already being included
.pc
An attempt has been made to include a file that is currently being
included in the program.
.errnote CO-02 '%s1' option cannot take a NO prefix
.pc
The compiler option %s1, cannot have the NO prefix specified.
The NO prefix is used to negate an option.
Certain options, including all options that require a value cannot have a
NO prefix.
.errnote CO-03 expecting an equals sign following the %s1 option
.pc
The compiler option %s1, requires an equal sign to be between the
option keyword and its associated value.
.errnote CO-04 the '%s1' option requires a number
.pc
The compiler option %s1 and an equal sign has been detected but the
required associated value is missing.
.errnote CO-05 option '%s1' not recognized - ignored
.pc
The option %s1 is not a recognized compiler option and has been ignored.
Consult the User's Guide for a complete list of compiler options.
.errnote CO-06 '%s1' option not allowed in source input stream
.pc
The option %s1 can only be specified on the command line.
Consult the User's Guide for a description of which options are allowed
in the source input stream.
.errnote CO-07 nesting level exceeded for compiler directives
.pc
Use of the C$IFDEF or C$IFNDEF compiler directives has caused the maximum
nesting level to be exceeded.
The maximum nesting level is 16.
.errnote CO-08 mismatching compiler directives
.pc
This error message is issued if, for example, a C$ENDIF directive is used and
no matching C$IFDEF or C$IFNDEF precedes it.
Incorrect nesting of C$IFDEF, C$IFNDEF, C$ELSE and C$ENDIF directives will
also cause this message to be issued.
.errtail
.errhead Compiler Errors
.errnote CP-01 program abnormally terminated
.pc
This message is issued during the execution of the program.
If you are running WATFOR-77, this message indicates that an internal error
has occurred in the compiler.
Please report this error and any other helpful information about the program
being compiled to Watcom so that the problem can be fixed.
.pc
If you are running an application compiled by the Watcom FORTRAN 77
optimizing compiler, this message may indicate a problem with the compiler
or a problem with your program.
Try compiling your application with the "debug" option.
This causes the generation of run-time checking code to validate, for
example, array subscripts and will help ensure that your program is not
in error.
.errnote CP-02 argument %d1 incompatible with register
.pc
The register specified in an auxiliary pragma for argument number %d1
is invalid.
.errnote CP-03 subprogram %s1 has invalid return register
.pc
The register specified in an auxiliary pragma for the return value of
function %s1 is invalid.
This error is issued when, for example, an auxiliary pragma is used to
specify EAX as the return register for a double precision function.
.errnote CP-04 low on memory - unable to fully optimize %s1
.pc
There is not enough memory for the code generator to fully optimize
subprogram %s1.
.errnote CP-05 internal compiler error %d1
.pc
This error is an internal code generation error.
Please report the specified internal compiler error number and any other
helpful information about the program being compiled to Watcom so that
the problem can be fixed.
.errnote CP-06 illegal register modified by %s1
.pc
An illegal register was said to be modified by %s1 in the auxiliary pragma
for %s1.
In a 32-bit flat memory model, the base pointer register EBP and segment
registers CS, DS, ES, and SS cannot be modified.
In small data models, the base pointer register (32-bit EBP or 16-bit BP)
and segment registers CS, DS, and SS cannot be modified.
In large data models, the base pointer register (32-bit EBP or 16-bit BP)
and segment registers CS, and SS cannot be modified.
.errnote CP-07 %s1
.pc
The message specified by %s1 indicates an error during the code generation
phase.
The most probable cause is an invalid instruction in the in-line assembly
code specified in an auxiliary pragma.
.errnote CP-08 fatal: %s1
.pc
The specified error indicates that the code generator has been abnormally
terminated.
This message will be issued if any internal limit is reached or a keyboard
interrupt sequence is pressed during the code generation phase.
.errnote CP-09 dynamic memory not freed
.pc
This message indicates an internal compiler error.
Please report this error and any other helpful information about the program
being compiled to Watcom so that the problem can be fixed.
.errnote CP-10 freeing unowned dynamic memory
.pc
This message indicates an internal compiler error.
Please report this error and any other helpful information about the program
being compiled to Watcom so that the problem can be fixed.
.errnote CP-11 The automatic equivalence containing %s1 exceeds 32K limit
.pc
In 16-bit environments, the size of an equivalence on the stack must not
exceed 32767 bytes.
.errnote CP-12 The return value of %s1 exceeds 32K limit
.pc
In 16-bit environments, the size of the return value of a function must not
exceed 32767 bytes.
.errnote CP-13 The automatic variable %s1 exceeds 32K limit
.pc
In 16-bit environments, the size of any variable on the stack must not
exceed 32767 bytes.
.errtail
.errhead Character Variables
.errnote CV-01 CHARACTER variable %s1 with length (*) not allowed in this expression
.pc
The length of the result of evaluating the expression is
indeterminate.
One of the operands has an indeterminate length and the result is
being assigned to a temporary.
.errnote CV-02 character variable %s1 with length (*) must be a subprogram argument
.pc
The character variable %s1 with a length specification (*) can only be
used to declare dummy arguments in the subprogram.
The length of a dummy argument assumes the length of the
corresponding actual argument.
.errtail
.errhead Data Initialization
.errnote DA-01 implied DO variable %s1 must be an integer variable
.pc
The implied DO variable %s1 must be declared as a variable of type
INTEGER or must have an implicit INTEGER type.
.errnote DA-02 repeat specification must be a positive integer
.pc
The repeat specification in the constant list of the DATA statement
must be an unsigned positive integer.
.errnote DA-03 %s1 appears in an expression but is not an implied DO variable
.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.
.errnote DA-04 %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.
.errnote DA-05 data initialization with hexadecimal constant is not FORTRAN 77 standard
.pc
Data initialization with hexadecimal constants is an extension to the
FORTRAN 77 language.
.errnote DA-06 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,