ferror.gml

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

statement.
.errnote IO-24 unit specified does not exist
.pc
The external unit identifier specified in the input/output statement
has not yet been connected.
Use preconnection or the OPEN statement to connect a file to the
external unit identifier.
.errnote IO-25 REC specifier is invalid
.pc
The REC specifier must be an unsigned positive integer.
.errnote IO-26 UNIT specifier is invalid
.pc
The UNIT specifier must be an unsigned integer between 0 and 999
inclusive.
.errnote IO-27 formatted record or format edit descriptor is too large for record size
.pc
This error is issued when the amount of formatted data in a READ, WRITE or
PRINT statement exceeds the maximum record size of the file.
The record size can be specified using the RECL= specified in the OPEN
statement.
.errnote IO-28 illegal '%s1=' specifier
.pc
In the OPEN or CLOSE statement the value associated with the %s1
specifier is not a valid value.
In the OPEN statement,
STATUS may only be one of OLD, NEW, SCRATCH or UNKNOWN;
ACCESS may only be one of SEQUENTIAL, APPEND or DIRECT;
FORM may only be one of FORMATTED or UNFORMATTED;
CARRIAGECONTROL may only be one of YES or NO;
RECORDTYPE may only be one of FIXED, TEXT or VARIABLE;
ACTION may only be one of READ, WRITE or READ/WRITE; and
BLANK may only be one of NULL, or ZERO.
In the CLOSE statement the STATUS may only be one of KEEP or DELETE.
.errnote IO-29 invalid CARRIAGECONTROL specifier/FORM specifier combination
.pc
The CARRIAGECONTROL specifier is only allowed with formatted i/o statements.
.errnote IO-30 i/o operation not consistent with file attributes
.pc
An attempt was made to read from a file that was opened with
ACTION=WRITE or write to a file that was opened with ACTION=READ.
This message is also issued if you attempt to write to a read-only file or
read from a write-only file.
.errnote IO-31 symbol %s1 not found in NAMELIST
.pc
During NAMELIST-directed input, a symbol was specified that does not belong
to the NAMELIST group specified in the i/o statement.
.errnote IO-32 syntax error during NAMELIST-directed input
.pc
Bad input was encountered during NAMELIST-directed input.
Data must be in a special form during NAMELIST-directed input.
.errnote IO-33 subscripting error during NAMELIST-directed i/o
.pc
An array was incorrectly subscripted during NAMELIST-directed input.
.errnote IO-34 substring error during NAMELIST-directed i/o
.pc
An character array element or variable was incorrectly substrung during
NAMELIST-directed input.
.errnote IO-35 BLOCKSIZE specifier is invalid
.pc
In the OPEN statement, the block size specifier must be a positive
integer expression.
.errnote IO-36 invalid operation for files with no record structure
.pc
An attempt has been made to perform an i/o operation on a file that requires
a record structure.
For example, it is illegal to use a BACKSPACE statement for a file that
has no record structure.
.errnote IO-37 integer overflow converting character data to integer
.pc
An overflow has occurred while converting the character data read to its
internal representation as an integer.
.errnote IO-38 range exceeded converting character data to floating-point
.pc
An overflow or underflow has occurred while converting the character data
read to its internal representation as a floating-point number.
.errtail
.errhead Program Termination
.errnote KO-01 floating-point divide by zero
.pc
An attempt has been made to divide a number by zero in a
floating-point expression.
.errnote KO-02 floating-point overflow
.pc
The floating-point expression result has exceeded the maximum
floating-point number.
.errnote KO-03 floating-point underflow
.pc
The floating-point expression result has exceeded the minimum
floating-point number.
.errnote KO-04 integer divide by zero
.pc
An attempt has been made to divide a number by zero in an integer
expression.
.errnote KO-05 program interrupted from keyboard
.pc
The user has interrupted the compilation or execution of a program
through use of the keyboard.
.errnote KO-06 integer overflow
.pc
The integer expression result has exceeded the maximum integer
number.
.errtail
.errhead Library Routines
.errnote LI-01 argument must be greater than zero
.pc
The argument to the intrinsic function must be greater than zero
(i.e., a positive number).
.errnote LI-02 absolute value of argument to arcsine, arccosine must not exceed one
.pc
The absolute value of the argument to the intrinsic function ASIN or
ACOS cannot be greater than or equal to the value 1.0.
.errnote LI-03 argument must not be negative
.pc
The argument to the intrinsic function must be greater than or equal
to zero.
.errnote LI-04 argument(s) must not be zero
.pc
The argument(s) to the intrinsic function must not be zero.
.errnote LI-05 argument of CHAR must be in the range zero to 255
.pc
The argument to the intrinsic function CHAR must be in the range 0 to
255 inclusive.
CHAR returns the character represented by an 8-bit pattern.
.errnote LI-06 %s1 intrinsic function cannot be passed 2 complex arguments
.pc
The second argument to the intrinsic function CMPLX and DCMPLX cannot
be a complex number.
.errnote LI-07 argument types must be the same for the %s1 intrinsic function
.pc
The second argument to the intrinsic function CMPLX or DCMPLX must be
of the same type as the first argument.
The second argument may only be used when the first argument is of
type INTEGER, REAL or DOUBLE PRECISION.
.errnote LI-08 expecting numeric argument, but %s1 argument was found
.pc
The argument to the intrinsic function, INT, REAL, DBLE, CMPLX, or
DCMPLX was of type %s1 and a numeric argument was expected.
.errnote LI-09 length of ICHAR argument greater than one
.pc
The length of the argument to the intrinsic function ICHAR must be of
type CHARACTER and length of 1.
ICHAR converts a character to its integer representation.
.errnote LI-10 cannot pass %s1 as argument to intrinsic function
.pc
The item %s1 cannot be used as an argument to an intrinsic function.
Only constants, simple variables, array elements, and substrung array
elements may be used as arguments.
.errnote LI-11 intrinsic function requires argument(s)
.pc
An attempt has been made to invoke an intrinsic function and no
actual arguments were listed.
.errnote LI-12 %s1 argument type is invalid for this generic function
.pc
The type of the argument used in the generic intrinsic function is
not correct.
.errnote LI-13 this intrinsic function cannot be passed as an argument
.pc
Only the specific name of the intrinsic function can be used as an
actual argument.
The generic name may not be used.
When the generic and intrinsic names are the same, use the INTRINSIC
statement.
.errnote LI-14 expecting %s1 argument, but %s2 argument was found
.pc
An argument of type %s2 was passed to a function but an argument of
type %s1 was expected.
.errnote LI-15 intrinsic function was assigned wrong type
.pc
The declared type of an intrinsic function does not agree with the
actual type.
.errnote LI-16 intrinsic function %s1 is not FORTRAN 77 standard
.pc
The specified intrinsic function is provided as an extension to the
FORTRAN 77 language.
.errnote LI-17 argument to ALLOCATED intrinsic function must be an allocatable array or character*(*) variable
.pc
The argument to the intrinsic function ALLOCATED must be an allocatable
array or character*(*) variable.
.errnote LI-18 invalid argument to ISIZEOF intrinsic function
.pc
The argument to the intrinsic function ISIZEOF must be a user-defined
structure name, a symbol name, or a constant.
.errtail
.errhead Mixed Mode
.errnote MD-01 relational operator has a logical operand
.pc
The operands of a relational expression must either be both
arithmetic or both character expressions.
The operand indicated is a logical expression.
.errnote MD-02 mixing DOUBLE PRECISION and COMPLEX types is not FORTRAN 77 standard
.pc
The mixing of items of type DOUBLE PRECISION and COMPLEX in an
expression is an extension to the FORTRAN 77 language.
.errnote MD-03 operator not expecting %s1 operands
.pc
Operands of type %s1 cannot be used with the indicated operator.
The operators **, /, *, +, and &minus. may only have numeric type data.
The operator // may only have character type data.
.errnote MD-04 operator not expecting %s1 and %s2 operands
.pc
Operands of conflicting type have been encountered.
For example, in a relational expression, it is not possible to compare a
character expression to an arithmetic expression.
Also, the type of the left hand operand of the field selection operator must
be a user-defined structure.
.errnote MD-05 complex quantities can only be compared using .EQ. or .NE.
.pc
Complex operands cannot be compared using less than (.LT.), less than
or equal (.LE.), greater than (.GT.), or greater than or equal (.GE.)
operators.
.errnote MD-06 unary operator not expecting %s1 type
.pc
The unary operators, + and &minus., may only be used with numeric types.
The unary operator .NOT. may be used only with a logical or integer operand.
The indicated operand was of type %s1 which is not one of the valid types.
.errnote MD-07 logical operator with integer operands is not FORTRAN 77 standard
.pc
Integer operands are permitted with the logical
operators .AND., .OR., .EQV., .NEQV., .NOT. and .XOR. as an extension to the
FORTRAN 77 language.
.errnote MD-08 logical operator %s1 is not FORTRAN 77 standard
.pc
The specified logical operator is an extension to the FORTRAN 77 standard.
.errtail
.errhead Memory Overflow
.errnote MO-01 %s1 exceeds compiler limit of %d2 bytes
.pc
An internal compiler limit has been reached.
%s1 describes the limit and %d2 specifies the limit.
.errnote MO-02 out of memory
.pc
All available memory has been used up.
During the compilation phase, memory is primarily used for the symbol table.
During execution, memory is used for file descriptors and buffers,
and dynamically allocatable arrays and character*(*) variables.
.errnote MO-03 dynamic memory exhausted due to length of this statement - statement ignored
.pc
There was not enough memory to encode the specified statement.
This message is usually issued when the compiler is low on memory or if the
statement is a very large statement that spans many continuation lines.
This error does not terminate the compiler since it may have been caused by
a very large statement.
The compiler attempts to compile the remaining statements.
.errnote MO-04 attempt to deallocate an unallocated array or character*(*) variable
.pc
An attempt has been made to deallocate an array that has not been previously
allocated.
An array or character*(*) variable must be allocated using an ALLOCATE
statement.
.errnote MO-05 attempt to allocate an already allocated array or character*(*) variable
.pc
An attempt has been made to allocate an array or character*(*) variable that
has been previously allocated in an ALLOCATE statement.
.errtail
.errhead Parentheses
.errnote PC-01 missing or misplaced closing parenthesis
.pc
An opening parenthesis '(' was found but no matching closing
parenthesis ')' was found before the end of the statement.
.errnote PC-02 missing or misplaced opening parenthesis
.pc
A closing parenthesis ')' was found before the matching opening
parenthesis '('.
.errnote PC-03 unexpected parenthesis
.pc
A parenthesis was found in a statement where parentheses are not
expected.
.errnote PC-04 unmatched parentheses
.pc
The parentheses in the expression are not balanced.
.errtail
.errhead PRAGMA Compiler Directive
.errnote PR-01 expecting symbolic name
.pc
Every auxiliary pragma must refer to a symbol.
This error is issued when the symbolic name is illegal or missing.
Valid symbolic names are formed from the following characters: a dollar
sign, an underscore, digits and any letter of the alphabet.
The first character of a symbolic name must be alphabetic, a dollar sign, or
an underscore.
.errnote PR-02 illegal size specified for VALUE attribute
.pc
The VALUE argument attribute of an auxiliary pragma contains in illegal
length specification.
Valid length specifications are 1, 2, 4 and 8.
.errnote PR-03 illegal argument attribute
.pc
An illegal argument attribute was specified.
Valid argument attributes are VALUE, REFERENCE, or DATA_REFERENCE.
.errnote PR-04 continuation line must contain a comment character in column 1
.pc
When continuing a line of an auxiliary pragma directive, the continued line
must end with a back-slash ('\') character and the continuation line must
begin with a comment character ('c', 'C' or '*') in column 1.
.errnote PR-05 expecting '%s1' near '%s2'
.pc
A syntax error was found while processing a PRAGMA directive.
%s1 identifies the expected information and %s2 identifies where in the
pragma the error occurred.
.errnote PR-06 in-line byte sequence limit exceeded