ferror.gml

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

.begnote
:DTHD.Subprogram Arguments
:DDHD.~b
.note AR-01
.bi 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.
.note AR-02
.bi dummy argument %s1 appears more than once
.pc
The same dummy argument %s1 is named more than once in the dummy
argument list.
.note AR-03
.bi argument number %d1 in call to %s2 must be CHARACTER*%d3 or bigger but size passed was %d4
.pc
Argument number %d1 in the call to subprogram %s2 was declared in the calling
subprogram to be CHARACTER*%d4.
In subprogram %s2, the argument was declared to be CHARACTER*%d3.
The size of the argument, in the calling program, must be greater
than or equal to the size in the subroutine/function.
.note AR-04
.bi argument number %d1 in call to %s2 - actual argument was %s3 but dummy argument was %s4
.pc
Argument number %d1 in the call to subprogram %s2 was a %s3 in the calling
subprogram but a %s4 in the called subprogram.
This message is issued when, for example, an function name is passed to
an array name.
.note AR-05
.bi argument number %d1 - %s2 was passed to an intrinsic function
.pc
Argument number %d1 to an intrinsic function was declared as a %s2 and cannot
be specified as an argument to an intrinsic function.
For example, it is illegal to pass an array to the SIN intrinsic function.
Constants, simple variables, array elements, and substrung array
elements may be used as arguments.
.note AR-06
.bi argument number %d1 in call to %s2 - a subroutine was passed but a function was expected
.pc
Argument number %d1 in the call to subprogram %s2 is a subroutine but
was used as a function in subprogram %s2.
.note AR-07
.bi number of arguments expected in call to %s1 was %d2, but found %d3
.pc
The number of arguments in the call to subprogram %s1 was %d3 and does not
match the definition of subprogram %s1 which was defined with %d2 arguments.
.note AR-08
.bi argument number %d1 in call to %s2 - a function was passed but a subroutine was expected
.pc
Argument number %d1 in the call to subprogram %s2 is a function but
was used as a subroutine in subprogram %s2.
.note AR-09
.bi argument number %d1 in call to %s2 - %s3 argument was passed but %s4 argument was expected
.pc
The type of argument number %d1 in the call to subprogram %s2 was %s3.
The type of argument number %d1 was declared as %s4 in subprogram %s2.
The number and types of actual and dummy arguments must match.
.note AR-10
.bi argument number %d1 in call to %s2 - type of structure passed does not match type of structure expected
.pc
The structure type of argument number %d1 in the call to subprogram
%s2 does not match the expected structure type.
Two structures are equivalent if the type of the corresponding field names
are the same.
Unions are considered equivalent if their sizes are the same.
Field names, and the structure name itself, do not have to be the same.
.note AR-11
.bi argument number %d1 in call to %s2 - argument passed by value but expected by reference
.pc
Argument number %d1 in the call to subprogram %s2 was passed by value.
The called subprogram expected the address of the argument instead of its
value.
.endnote
.begnote
:DTHD.Block Data Subprograms
:DDHD.~b
.note BD-01
.bi %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.
.note BD-02
.bi %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.
.endnote
.begnote
:DTHD.Source Format and Contents
:DDHD.~b
.note CC-01
.bi 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.
.note CC-02
.bi 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.
.note CC-03
.bi 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.
.note CC-04
.bi 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.
.note CC-05
.bi 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.
.note CC-06
.bi more than 19 continuation lines is not FORTRAN 77 standard
.pc
More than 19 continuation lines is an extension to the FORTRAN 77 language.
.note CC-07
.bi 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.
.note CC-08
.bi 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.
.note CC-09
.bi 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.
.endnote
.begnote
:DTHD.COMMON Blocks
:DDHD.~b
.note CM-01
.bi %s1 already in COMMON
.pc
The variable or array name, %s1, has already been specified in this or
another COMMON block.
.note CM-02
.bi 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.
.note CM-03
.bi 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.
.note CM-04
.bi 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.
.note CM-05
.bi 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.
.note CM-06
.bi 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.
.endnote
.begnote
:DTHD.Constants
:DDHD.~b
.note CN-01
.bi 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.
.note CN-02
.bi 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.
.note CN-03
.bi zero length character constants are not allowed
.pc
FORTRAN 77 does not allow character constants of length 0 (i.e., an
empty string).
.note CN-04
.bi 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'.
.note CN-05
.bi hexadecimal/octal constant is not FORTRAN 77 standard
.pc
Hexadecimal and octal constants are extensions to the FORTRAN 77 standard.
.endnote
.begnote
:DTHD.Compiler Options
:DDHD.~b
.note CO-01
.bi %s1 is already being included
.pc
An attempt has been made to include a file that is currently being
included in the program.
.note CO-02
.bi '%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.
.note CO-03
.bi 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.
.note CO-04
.bi 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.
.note CO-05
.bi 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.
.note CO-06
.bi '%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.
.note CO-07
.bi 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.
.note CO-08
.bi 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.
.note CO-09
.bi DATA option not allowed
.pc
A source file has been included into the current program through the
use of the INCLUDE compiler option.
This included source file cannot contain the DATA compiler option.
.note CO-10
.bi maximum limit exceeded in the '%s1' option - option ignored
.pc
The user has specified a value on an option which exceeds the maximum allowed
value.
.note CO-11
.bi DATA option not allowed with OBJECT option
.pc
The DATA compiler option can not appear a file that is compiled with the
OBJECT option.
.endnote
.begnote
:DTHD.Compiler Errors
:DDHD.~b
.note CP-01
.bi 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.
.note CP-09
.bi 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.
.note CP-10
.bi 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.
.endnote
.begnote
:DTHD.Character Variables
:DDHD.~b
.note CV-01
.bi 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.
.note CV-02
.bi 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.
.note CV-03
.bi left and right hand sides overlap in a character assignment statement
.pc
The expression on the right hand side defines a substring of a
character variable and tries to assign it to an overlapping part of
the same character variable.
.endnote
.begnote
:DTHD.Data Initialization
:DDHD.~b
.note DA-01
.bi 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.
.note DA-02
.bi 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.
.note DA-03
.bi %s1 appears in an expression but is not an implied DO variable