ferror.gml

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

has been read or written.
.note IO-17
.bi invalid RECL specifier/ACCESS specifier combination
.pc
In the OPEN statement, if the ACCESS specifier is DIRECT then the
RECL specifier must be given.
.note IO-18
.bi REC specifier required in direct access input/output statements
.pc
In the OPEN statement, the ACCESS  specified was DIRECT.
All subsequent input/output statements for that file must use the REC
specifier to indicate which record to access.
.note IO-19
.bi REC specifier not allowed in sequential access input/output statements
.pc
In the OPEN statement, the ACCESS specified was SEQUENTIAL.
The REC specifier may not be used in subsequent I/O statements for
that file.
The REC specifier is used to indicate which record to access when
access is DIRECT.
.note IO-20
.bi %s1 specifier may not change in a subsequent OPEN statement
.pc
The %s1 specifier may not be changed on a subsequent OPEN statement
for the same file, in the same program.
Only the BLANK specifier may be changed.
.note IO-21
.bi invalid STATUS specifier for given file
.pc
In the OPEN statement, the STATUS specifier does not match with the
actual file status: OLD means the file must exist, NEW means the file
must not exist.
If the STATUS specifier is omitted, UNKNOWN is assumed.
.note IO-22
.bi invalid STATUS specifier/FILE specifier combination
.pc
In the OPEN statement, if the STATUS is SCRATCH, the FILE specifier
cannot be used.
If the STATUS is NEW or OLD, the FILE specifier must be given.
.note IO-23
.bi record size exceeded during unformatted input/output
.pc
This error is issued when the size of an i/o list item exceeds the
maximum record size of the file.
The record size can be specified using the RECL= specified in the OPEN
statement.
.note IO-24
.bi 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.
.note IO-25
.bi REC specifier is invalid
.pc
The REC specifier must be an unsigned positive integer.
.note IO-26
.bi UNIT specifier is invalid
.pc
The UNIT specifier must be an unsigned integer between 0 and 999
inclusive.
.note IO-27
.bi 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.
.note IO-28
.bi 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.
.note IO-29
.bi invalid CARRIAGECONTROL specifier/FORM specifier combination
.pc
The CARRIAGECONTROL specifier is only allowed with formatted i/o statements.
.note IO-30
.bi 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.
.note IO-31
.bi 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.
.note IO-32
.bi 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.
.note IO-33
.bi subscripting error during NAMELIST-directed i/o
.pc
An array was incorrectly subscripted during NAMELIST-directed input.
.note IO-34
.bi substring error during NAMELIST-directed i/o
.pc
An character array element or variable was incorrectly substrung during
NAMELIST-directed input.
.note IO-35
.bi BLOCKSIZE specifier is invalid
.pc
In the OPEN statement, the block size specifier must be a positive
integer expression.
.note IO-36
.bi 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.
.endnote
.begnote
:DTHD.Program Termination
:DDHD.~b
.note KO-01
.bi floating-point divide by zero
.pc
An attempt has been made to divide a number by zero in a
floating-point expression.
.note KO-02
.bi floating-point overflow
.pc
The floating-point expression result has exceeded the maximum
floating-point number.
.note KO-03
.bi floating-point underflow
.pc
The floating-point expression result has exceeded the minimum
floating-point number.
.note KO-04
.bi integer divide by zero
.pc
An attempt has been made to divide a number by zero in an integer
expression.
.note KO-05
.bi program interrupted from keyboard
.pc
The user has interrupted the compilation or execution of a program
through use of the keyboard.
.note KO-06
.bi integer overflow
.pc
The integer expression result has exceeded the maximum integer
number.
.note KO-07
.bi maximum pages of output exceeded
.pc
The specified maximum number of output pages has been exceeded.
The maximum number of output pages can be increased
by using the "pages=n" option in the command line
or specifying C$PAGES=n in the source file.
.note KO-08
.bi statement count has been exceeded
.pc
The maximum number of source statements has been executed.
The maximum number of source statements that can be executed can be
increased by using the "statements=n" option in the command line or
specifying C$STATEMENTS=n in the source file.
.note KO-09
.bi time limit exceeded
.pc
The maximum amount of time for program execution has been exceeded.
The maximum amount of time can be increased
by using the "time=t" option in the command line or specifying C$TIME=t
in the source file.
.endnote
.begnote
:DTHD.Library Routines
:DDHD.~b
.note LI-01
.bi argument must be greater than zero
.pc
The argument to the intrinsic function must be greater than zero
(i.e., a positive number).
.note LI-02
.bi 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.
.note LI-03
.bi argument must not be negative
.pc
The argument to the intrinsic function must be greater than or equal
to zero.
.note LI-04
.bi argument(s) must not be zero
.pc
The argument(s) to the intrinsic function must not be zero.
.note LI-05
.bi 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.
.note LI-06
.bi %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.
.note LI-07
.bi 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.
.note LI-08
.bi 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.
.note LI-09
.bi 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.
.note LI-10
.bi 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.
.note LI-11
.bi intrinsic function requires argument(s)
.pc
An attempt has been made to invoke an intrinsic function and no
actual arguments were listed.
.note LI-12
.bi %s1 argument type is invalid for this generic function
.pc
The type of the argument used in the generic intrinsic function is
not correct.
.note LI-13
.bi 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.
.note LI-14
.bi 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.
.note LI-15
.bi intrinsic function was assigned wrong type
.pc
The declared type of an intrinsic function does not agree with the
actual type.
.note LI-16
.bi intrinsic function %s1 is not FORTRAN 77 standard
.pc
The specified intrinsic function is provided as an extension to the
FORTRAN 77 language.
.note LI-17
.bi argument to ALLOCATED intrinsic function must be an allocatable array
.pc
The argument to the intrinsic function ALLOCATED must be an allocatable
array.
.note LI-18
.bi 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.
.endnote
.begnote
:DTHD.Mixed Mode
:DDHD.~b
.note MD-01
.bi 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.
.note MD-02
.bi 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.
.note MD-03
.bi 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.
.note MD-04
.bi 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.
.note MD-05
.bi 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.
.note MD-06
.bi 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.
.note MD-07
.bi 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.
.note MD-08
.bi logical operator %s1 is not FORTRAN 77 standard
.pc
The specified logical operator is an extension to the FORTRAN 77 standard.
.endnote
.begnote
:DTHD.Memory Overflow
:DDHD.~b
.note MO-01
.bi %s1 exceeds compiler limit of %d2 bytes
.pc
An internal compiler limit has been reached.
%s1 describes the limit and %d2 specifies the limit.
.note MO-02
.bi dynamic memory exhausted
.pc
The dynamic memory has been entirely used up.
During the compilation phase, dynamic memory is primarily used for the
symbol table.
During execution, dynamic memory is used for file descriptors and buffers,
and dynamically allocatable arrays.
.note MO-03
.bi 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.
.note MO-04
.bi attempt to deallocate an unallocated array
.pc
An attempt has been made to deallocate an array that has not been previously