ferror.gml

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

allocated.
An array must be allocated using an ALLOCATE statement.
.note MO-05
.bi attempt to allocate an already allocated array
.pc
An attempt has been made to allocate an array that has been previously
allocated in an ALLOCATE statement.
.note MO-06
.bi object memory exhausted
.pc
The amount of object code generated for the program has exceeded the amount
of memory allocated to store the object code.
The "/codesize" option can be used to increase the amount of memory
allocated for object code.
.endnote
.begnote
:DTHD.Parentheses
:DDHD.~b
.note PC-01
.bi missing or misplaced closing parenthesis
.pc
An opening parenthesis '(' was found but no matching closing
parenthesis ')' was found before the end of the statement.
.note PC-02
.bi missing or misplaced opening parenthesis
.pc
A closing parenthesis ')' was found before the matching opening
parenthesis '('.
.note PC-03
.bi unexpected parenthesis
.pc
A parenthesis was found in a statement where parentheses are not
expected.
.note PC-04
.bi unmatched parentheses
.pc
The parentheses in the expression are not balanced.
.endnote
.begnote
:DTHD.PRAGMA Compiler Directive
:DDHD.~b
.note PR-01
.bi 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 underscrore, digits and any letter of the alphabet.
The first character of a symbolic name must be alphabetic, a dollar sign, or
an underscore.
.note PR-02
.bi 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.
.note PR-03
.bi illegal argument attribute
.pc
An illegal argument attribute was specified.
Valid argument attributes are VALUE, REFERENCE, or DATA_REFERENCE.
.note PR-04
.bi 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.
.note PR-05
.bi 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.
.endnote
.begnote
:DTHD.RETURN Statement
:DDHD.~b
.note RE-01
.bi alternate return specifier only allowed in subroutine
.pc
An alternate return specifier, in the RETURN statement, may only be
specified when returning from a subroutine.
.note RE-02
.bi RETURN statement in main program is not FORTRAN 77 standard
.pc
A RETURN statement in the main program is allowed as an extension to the
FORTRAN 77 standard.
.endnote
.begnote
:DTHD.SAVE Statement
:DDHD.~b
.note SA-01
.bi COMMON block %s1 saved but not properly defined
.pc
The named COMMON block %s1 was listed in a SAVE statement but there is
no named COMMON block defined by that name.
.note SA-02
.bi COMMON block %s1 must be saved in every subprogram in which it appears
.pc
The named COMMON block %s1 appears in a SAVE statement in another
subprogram and is not in a SAVE statement in this subprogram.
If a named COMMON block is specified in a SAVE statement in a
subprogram, it must be specified in a SAVE statement in every
subprogram in which that COMMON block appears.
.note SA-03
.bi name already appeared in a previous SAVE statement
.pc
The indicated name has already been referenced in another SAVE
statement in this subprogram.
.endnote
.begnote
:DTHD.Statement Functions
:DDHD.~b
.note SF-01
.bi statement function definition contains duplicate dummy arguments
.pc
A dummy argument is repeated in the argument list of the statement function.
.note SF-02
.bi character length of statement function name must not be (*)
.pc
If the type of a character function is character, its length specification
must not be (*); it must be a constant integer expression.
.note SF-03
.bi statement function definition contains illegal dummy argument
.pc
A dummy argument of type CHARACTER must have a length specification
of an integer constant expression that is not (*).
.note SF-04
.bi cannot pass %s1 %s2 to statement function
.pc
The actual arguments to a statement function can be any expression
except character expressions involving the concatenation of an
operand whose length specification is (*) unless the operand is a
symbolic constant.
.note SF-05
.bi %s1 actual argument was passed to %s2 dummy argument
.pc
The indicated actual argument is of type %s1 which is not the same
type as that of the dummy argument of type %s2.
.note SF-06
.bi incorrect number of arguments passed to statement function %s1
.pc
The number of arguments passed to statement function %s1 does not
agree with the number of dummy arguments specified in its definition.
.note SF-07
.bi type of statement function name must not be a user-defined structure
.pc
The type of a statement function cannot be a user-defined structure.
Valid types for statement functions are: LOGICAL*1, LOGICAL, INTEGER*1,
INTEGER*2, INTEGER, REAL, DOUBLE PRECISION, COMPLEX, DOUBLE COMPLEX, and
CHARACTER.
If the statement function is of type CHARACTER, its length specification
must not be (*); it must be an integer constant expression.
.endnote
.begnote
:DTHD.Source Management
:DDHD.~b
.note SM-01
.bi system file error reading %s1 - %s2
.pc
An I/O error, described by %s2, has occurred while reading the
FORTRAN source file %s1.
.note SM-02
.bi error opening file %s1 - %s2
.pc
The FORTRAN source file %s1 could not be opened.
The error is described by %s2.
.note SM-03
.bi system file error writing %s1 - %s2
.pc
An I/O error, described by %s2, has occurred while writing to the
file %s1.
.note SM-04
.bi error spawning %s1 - %s2
.pc
An error, described by %s2, occurred while trying to spawn the external
program named %s1.
.note SM-05
.bi error while linking
.pc
An error occurred while trying to create the executable file.  See the
WLINK documentation for a description of the error.
.endnote
.begnote
:DTHD.Structured Programming Features
:DDHD.~b
.note SP-01
.bi cannot have both ATEND and the END= specifier
.pc
It is not valid to use the AT END control statement and the END=
option on the READ statement.
Only one method can be used to control the end-of-file condition.
.note SP-02
.bi ATEND must immediately follow a READ statement
.pc
The indicated AT END control statement or block does not immediately
follow a READ statement.
The AT END control statement or block is executed when an end-of-file
condition is encountered during the read.
.note SP-03
.bi block label must be a symbolic name
.pc
The indicated block label must be a symbolic name.
A symbolic name must start with a letter and contain no more than 32
letters and digits.
A letter is an upper or lower case letter of the alphabet, a dollar sign ($),
or an underscore (_).
A digit is a character in the range '0' to '9'.
.note SP-04
.bi could not find a structure to %s1 from
.pc
This message is issued in the following cases.
.autonote
.note
There is no control structure to QUIT from.
The QUIT statement will transfer control to the statement following the
currently active control structure or return from a REMOTE BLOCK if no
other control structures are active within the REMOTE BLOCK.
.note
There is no control structure to EXIT from.
The EXIT statement is used to exit a loop-processing structure such as
DO, DO WHILE, WHILE and LOOP, to return from a REMOTE BLOCK regardless of the
number of active control structures within the REMOTE BLOCK, or to transfer
control from a GUESS or ADMIT block to the statement following the ENDGUESS
statement.
.note
There is no active looping control structure from which a CYCLE statement
can be used.
A CYCLE statement can only be used within a
DO, DO WHILE, WHILE and LOOP control structure.
.endnote
.note SP-05
.bi REMOTE BLOCK is not allowed in the range of any control structure
.pc
An attempt has been made to define a REMOTE BLOCK inside a control
structure.
Control structures include IF, LOOP, WHILE, DO, SELECT and GUESS.
When a REMOTE BLOCK definition is encountered during execution,
control is transferred to the statement following the corresponding
END BLOCK statement.
.note SP-06
.bi the SELECT statement must be followed immediately by a CASE statement
.pc
The statement immediately after the SELECT statement must be a CASE
statement.
The SELECT statement allows one of a number of blocks of code (case
blocks) to be selected for execution by means of an integer
expression in the SELECT statement.
.note SP-07
.bi cases are overlapping
.pc
The case lists specified in the CASE statements in the SELECT control
structure are in conflict.
Each case list must specify a unique integer constant expression or
range.
.note SP-08
.bi select structure requires at least one CASE statement
.pc
In the SELECT control structure, there must be at least one CASE
statement.
.note SP-09
.bi cannot branch to %d1 from outside control structure in line %d2
.pc
The statement in line %d2 passes control to the statement %d1 in a
control structure.
Control may only be passed out of a control structure or to another
place in that control structure.
Control structures include DO, GUESS, IF, LOOP, SELECT, and WHILE.
.note SP-10
.bi cannot branch to %d1 inside structure on line %d2
.pc
The statement attempts to pass control to statement %d1 in line %d2
which is in a control structure.
Control may only be passed out of a control structure or to another
place in that control structure.
Control structures include DO, GUESS, IF, LOOP, SELECT, and WHILE.
.note SP-11
.bi low end of range exceeds the high end
.pc
The first number, the low end of the range, is greater than the
second number, the high end of the range.
.note SP-12
.bi default case block must follow all case blocks
.pc
The default case block in the SELECT control structure must be the last
case block.
A case block may not follow the default case block.
.note SP-13
.bi attempt to branch out of a REMOTE BLOCK
.pc
An attempt has been made to transfer execution control out of a
REMOTE BLOCK.
A REMOTE BLOCK may only be terminated with the END BLOCK statement.
Execution of a REMOTE BLOCK is similar in concept to execution of a
subroutine.
.note SP-14
.bi attempt to EXECUTE undefined REMOTE BLOCK %s1
.pc
The REMOTE BLOCK %s1 referenced in the EXECUTE statement does not
exist in the current program unit.
A REMOTE BLOCK is local to the program unit in which it is defined
and may not be referenced from another program unit.
.note SP-15
.bi attempted to use REMOTE BLOCK recursively
.pc
An attempt was made to execute a REMOTE BLOCK which was already
active.
.note SP-16
.bi cannot RETURN from subprogram within a REMOTE BLOCK
.pc
An illegal attempt has been made to execute a RETURN statement within
a REMOTE BLOCK in a subprogram.
.note SP-17
.bi %s1 statement is not FORTRAN 77 standard
.pc
The statement %s1 is an extension to the FORTRAN 77 language.
.note SP-18
.bi %s1 block is unfinished
.pc
The block starting with the statement %s1 does not have the ending
block statement.
For example: ATENDDO-ENDATEND, DO-ENDDO, GUESS-ENDGUESS, IF-ENDIF,
LOOP-ENDLOOP, SELECT-ENDSELECT, STRUCTURE-ENDSTRUCTURE and WHILE-ENDWHILE.
.note SP-19
.bi %s1 statement does not match with %s2 statement
.pc
The statement %s1, which ends a control structure, cannot be used with
statement %s2 to form a control structure.
Valid control structures are: LOOP - ENDLOOP, LOOP - UNTIL, WHILE -
ENDWHILE, and WHILE - UNTIL.
.note SP-20
.bi incomplete control structure found at %s1 statement
.pc
The ending control structure statement %s1 was found and there was no
preceding matching beginning statement.
Valid control structures include: ATENDDO - ENDATEND, GUESS -
ENDGUESS, IF - ENDIF, LOOP - ENDLOOP, REMOTE BLOCK - ENDBLOCK, and
SELECT - ENDSELECT.
.note SP-21
.bi %s1 statement is not allowed in %s2 definition
.pc
Statement %s1 is not allowed between a %s2 statement and the
corresponding END %s2 statement.
For example, an EXTERNAL statement is not allowed between a STRUCTURE and
END STRUCTURE statement, a UNION and END UNION statement, or a MAP and
END MAP statement.
.note SP-22
.bi no such field name found in structure %s1
.pc
A structure reference contained a field name that does not belong to the
specified structure.
.note SP-23
.bi multiple definition of field name %s1
.pc
The field name %s1 has already been defined in a structure.
.note SP-24
.bi structure %s1 has not been defined
.pc
An attempt has been ma