ferror.gml

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

The repeat specification of the indicated edit descriptor is greater
than the maximum allowed of 256.
.note FM-15
.bi invalid field width specification
.pc
The width specifier on the indicated edit descriptor is invalid.
.note FM-16
.bi Z format code is not FORTRAN 77 standard
.pc
The Z (hexadecimal format) repeatable edit descriptor is an extension
to the FORTRAN 77 language.
.note FM-17
.bi FORMAT statement exceeds allotted storage size
.pc
The maximum allowable size of a FORMAT statement has exceeded.
The statement must be split into two or more FORMAT statements.
.note FM-18
.bi format specification not allowed on input
.pc
A format specification, in the FORMAT statement, is not allowed to be
used as an input specification.
Valid specifications include: T, TL,TR, X, /, :, P, BN, BZ, I, F, E,
D, G, L, A, and Z.
.note FM-19
.bi FORMAT missing repeatable edit descriptor
.pc
An attempt has been made to read or write a piece of data without a
valid repeatable edit descriptor.
All data requires a repeatable edit descriptor in the format.
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-20
.bi missing constant before X edit descriptor, 1 assumed
.pc
The omission of the constant before an X edit descriptor in a format
specification is an extension to the FORTRAN 77 language.
.endnote
.begnote
:DTHD.GOTO and ASSIGN Statements
:DDHD.~b
.note GO-01
.bi %s1 statement label may not appear in ASSIGN statement but did in line %d2
.pc
The statement label in the ASSIGN statement in line %d2 references a
%s1 statement.
The statement label in the ASSIGN statement must appear in the same
program unit and must be that of an executable statement or a FORMAT
statement.
.note GO-02
.bi ASSIGN of statement number %d1 in line %d2 not allowed
.pc
The statement label %d1 in the ASSIGN statement is used in the line
%d2 which references a non-executable statement.
A statement label must appear in the same program unit as the ASSIGN
statement and must be that of an executable statement or a FORMAT
statement.
.note GO-03
.bi expecting TO
.pc
The keyword TO is missing or misplaced in the ASSIGN statement.
.endnote
.begnote
:DTHD.Hollerith Constants
:DDHD.~b
.note HO-01
.bi hollerith constant is not FORTRAN 77 standard
.pc
Hollerith constants are an extension to the FORTRAN 77 language.
.note HO-02
.bi not enough characters for hollerith constant
.pc
The number of characters following the H or h is not equal to the
constant preceding the H or h.
A hollerith constant consists of a positive unsigned integer constant
n followed by the letter H or h followed by a string of exactly n
characters.
.endnote
.begnote
:DTHD.IF Statements
:DDHD.~b
.note IF-01
.bi ELSE block must be the last block in block IF
.pc
Another ELSE IF block has been found after the ELSE block.
The ELSE block must be the last block in an IF block.
The form of the block IF is as follows:
.millust begin
IF (logical expression) THEN [:block-label]
         {statement}
{ ELSE IF
         {statement} }
[ELSE
         {statement}  ]
ENDIF
.millust end
.note IF-02
.bi expecting THEN
.pc
The keyword THEN is missing or misplaced in the block IF statement.
The form of the block IF is as follows:
.millust begin
IF (logical expression) THEN [:block-label]
         {statement}
{ ELSE IF
         {statement} }
[ELSE
         {statement}  ]
ENDIF
.millust end
.endnote
.begnote
:DTHD.I/O Lists
:DDHD.~b
.note IL-01
.bi missing or invalid format/FMT specification
.pc
A valid format specification is required on all READ and WRITE
statements.
The format specification is specified by:
.millust begin
[FMT=] <format identifier>
.millust end
.pc
.sy <format identifier>
is one of the following: statement label, integer variable-name,
character array-name, character expression, or *.
.note IL-02
.bi the UNIT may not be an internal file for this statement
.pc
An internal file may only be referenced in a READ or WRITE statement.
An internal file may not be referenced in a BACKSPACE, CLOSE,
ENDFILE, INQUIRE, OPEN, or REWIND statement.
.note IL-03
.bi %s1 statement cannot have %s2 specification
.pc
The I/O statement %s1 may not have the control information %s2
specified.
.note IL-04
.bi variable must have a size of 4
.pc
The variable used as a specifier in an I/O statement must be of size
4 but another size was specified.
These include the EXIST, OPENED, RECL, IOSTAT, NEXTREC, and NUMBER.
The name used in the ASSIGN statement must also be of size 4 but a
different size was specified.
.note IL-05
.bi missing or unrecognizable control list item %s1
.pc
A control list item %s1 was encountered in an I/O statement and is not
a valid control list item for that statement, or a control list item
was expected and was not found.
.note IL-06
.bi attempt to specify control list item %s1 more than once
.pc
The control list item %s1 in the indicated I/O statement, has been
named more than once.
.note IL-07
.bi implied DO loop has no input/output list
.pc
The implied DO loop specified in the I/O statement does not
correspond with a variable or expression in the input/output list.
.note IL-08
.bi list-directed input/output with internal files is not FORTRAN 77 standard
.pc
List-directed input/output with internal files is an extension to the
FORTRAN 77 language.
.note IL-09
.bi FORTRAN 77 standard requires an asterisk for list-directed formatting
.pc
An optional asterisk for list-directed formatting is an extension to
the FORTRAN 77 language.
The standard FORTRAN 77 language specifies that an asterisk is required.
.note IL-10
.bi missing or improper unit identification
.pc
The control specifier, UNIT, in the I/O statement is either missing
or identifies an improper unit.
The unit specifier specifies an external unit or internal file.
The external unit identifier is a non-negative integer expression or
an asterisk.
The internal file identifier is character variable, character array,
character array element, or character substring.
.note IL-11
.bi missing unit identification or file specification
.pc
An identifier to specifically identify the required file is missing.
The UNIT specifier is used to identify the external unit or internal
file.
The FILE specifier in the INQUIRE and OPEN statements is used to
identify the file name.
.note IL-12
.bi asterisk unit identifier not allowed in %s1 statement
.pc
The BACKSPACE, CLOSE, ENDFILE, INQUIRE, OPEN, and REWIND statements
require the external unit identifier be an unsigned positive integer
from 0 to 999.
.note IL-13
.bi cannot have both UNIT and FILE specifier
.pc
There are two valid forms of the INQUIRE statement; INQUIRE by FILE
and INQUIRE by UNIT.
Both of these specifiers cannot be specified in the same statement.
.note IL-14
.bi internal files require sequential access
.pc
An attempt has been made to randomly access an internal file.
Internal files may only be accessed sequentially.
.note IL-15
.bi END specifier with REC specifier is not FORTRAN 77 standard
.pc
The FORTRAN 77 standard specifies that an end-of-file condition can only
occur with a file connected for sequential access or an internal file.
The REC specifier indicates that the file is connected for direct access.
This extension allows the programmer to detect an end-of-file condition when
reading the records sequentially from a file connected for direct access.
.note IL-16
.bi %s1 specifier in i/o list is not FORTRAN 77 standard
.pc
The specified i/o list item is provided as an extension to the
FORTRAN 77 language.
.note IL-17
.bi i/o list is not allowed with NAMELIST-directed format
.pc
An i/o list is not allowed when the format specification is a NAMELIST.
.note IL-18
.bi non-character array as format specifier is not FORTRAN 77 standard
.pc
A format specifier must be of type character unless it is an array name.
Allowing a non-character array name is an extension to the FORTRAN 77 standard.
.endnote
.begnote
:DTHD.IMPLICIT Statements
:DDHD.~b
.note IM-01
.bi illegal range of characters
.pc
In the IMPLICIT statement, the first letter in the range of
characters must be smaller in the collating sequence than
the second letter in the range.
.note IM-02
.bi letter can only be implicitly declared once
.pc
The indicated letter has been named more than once in this or a
previous IMPLICIT statement.
A letter may only be named once.
.note IM-03
.bi unrecognizable type
.pc
The type declared in the IMPLICIT statement is not one of INTEGER,
REAL, DOUBLE PRECISION, COMPLEX, LOGICAL or CHARACTER.
.note IM-04
.bi (*) length specifier in an IMPLICIT statement is not FORTRAN 77 standard
.pc
A character length specified of (*) in an IMPLICIT statement is an
extension to the FORTRAN 77 language.
.note IM-05
.bi IMPLICIT NONE allowed once or not allowed with other IMPLICIT statements
.pc
The IMPLICIT NONE statement must be the only IMPLICIT statement in
the program unit in which it appears.
Only one IMPLICIT NONE statement is allowed in a program unit.
.endnote
.begnote
:DTHD.Input/Output
:DDHD.~b
.note IO-01
.bi BACKSPACE statement requires sequential access mode
.pc
The file connected to the unit specified in the BACKSPACE statement
has not been opened for sequential access.
.note IO-02
.bi input/output is already active
.pc
An attempt has been made to read or write a record when there is an
already active read or write in progress.
The execution of a READ or WRITE statement has caused transfer to a
function that contains a READ or WRITE statement.
.note IO-03
.bi ENDFILE statement requires sequential access mode
.pc
The specified external unit identifier must be connected for
sequential access but was connected for direct access.
.note IO-04
.bi formatted connection requires formatted input/output statements
.pc
The FORM specifier in the OPEN statement specifies FORMATTED and the
subsequent READ and/or WRITE statement does not use formatted I/O.
If the FORM specifier has been omitted and access is SEQUENTIAL then
FORMATTED is assumed.
If the access is DIRECT then UNFORMATTED is assumed.
.note IO-05
.bi unformatted connection requires unformatted input/output statements
.pc
The FORM specifier in the OPEN statement specifies UNFORMATTED and
the subsequent READ and/or WRITE statement uses formatted I/O.
If the FORM specifier has been omitted and access is SEQUENTIAL then
FORMATTED is assumed.
If the access is DIRECT then UNFORMATTED is assumed.
.note IO-06
.bi REWIND statement requires sequential access
.pc
The external unit identifier is not connected to a sequential file.
The REWIND statement positions to the first record in the file.
.note IO-07
.bi bad character in input field
.pc
The data received from the record in a file does not match the type
of the input list item.
.note IO-08
.bi BLANK specifier requires FORM specifier to be 'FORMATTED'
.pc
In the OPEN statement, the BLANK specifier may only be used when the
FORM specifier has the value of FORMATTED.
The BLANK specifier indicates whether blanks are treated as zeroes or
ignored.
.note IO-09
.bi system file error - %s1
.pc
A system error has occurred while attempting to access a file.
The I/O system error message is displayed.
.note IO-10
.bi format specification does not match data type
.pc
A format specification in the FMT specifier or FORMAT statement
specifies data of one type and the variable list specifies data of a
different type.
.note IO-11
.bi input item does not match the data type of list variable
.pc
In the READ statement, the data type of a variable listed is not of
the same data type in the data file.
For example, non-digit character data being read into an integer
item.
.note IO-12
.bi internal file is full
.pc
The internal file is full of data.
If a file is a variable then the file may only contain one record.
If the file is a character array then there can be one record for
each array element.
.note IO-13
.bi RECL specifier is invalid
.pc
In the OPEN statement, the record length specifier must be a positive
integer expression.
.note IO-14
.bi invalid STATUS specifier in CLOSE statement
.pc
The STATUS specifier can only have a value of KEEP or DELETE.
If the STATUS in the OPEN statement is SCRATCH then the KEEP status
on the CLOSE statement cannot be used.
.note IO-15
.bi unit specified is not connected
.pc
The unit number specified in the I/O statement has not been
previously connected.
.note IO-16
.bi attempt to perform data transfer past end of file
.pc
An attempt has been made to read or write data after the end of file