ferror.gml

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

.pc
The limit on the number of bytes of code that can be generated in-line using
a an auxiliary pragma has been exceeded.
The limit is 127 bytes.
.errnote PR-07 illegal hexadecimal data in byte sequence
.pc
An illegal hexadecimal constant was encountered while processing a in-line
byte sequence of an auxiliary pragma.
Valid hexadecimal constants in an in-line byte sequence must begin with the
letter Z or z and followed by a string of hexadecimal digits.
.errnote PR-08 symbol '%s1' in in-line assembly code cannot be resolved
.pc
The symbol %s1, referenced in an assembly language instruction in an
auxiliary pragma, could not be resolved.
.errtail
.errhead RETURN Statement
.errnote RE-01 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.
.errnote RE-02 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.
.errtail
.errhead SAVE Statement
.errnote SA-01 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.
.errnote SA-02 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.
.errnote SA-03 name already appeared in a previous SAVE statement
.pc
The indicated name has already been referenced in another SAVE
statement in this subprogram.
.errtail
.errhead Statement Functions
.errnote SF-01 statement function definition contains duplicate dummy arguments
.pc
A dummy argument is repeated in the argument list of the statement function.
.errnote SF-02 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.
.errnote SF-03 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 (*).
.errnote SF-04 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.
.errnote SF-05 %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.
.errnote SF-06 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.
.errnote SF-07 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.
.errtail
.errhead Source Management
.errnote SM-01 system file error reading %s1 - %s2
.pc
An I/O error, described by %s2, has occurred while reading the
FORTRAN source file %s1.
.errnote SM-02 error opening file %s1 - %s2
.pc
The FORTRAN source file %s1 could not be opened.
The error is described by %s2.
.errnote SM-03 system file error writing %s1 - %s2
.pc
An I/O error, described by %s2, has occurred while writing to the
file %s1.
.errnote SM-06 error opening %s1 - too many temporary files exist
.pc
The compiler was not able to open a temporary file for intermediate storage
during code generation.
Temporary files are created in the directory specified by the TMP
environment variable.
If the TMP environment variable is not set, the temporary file is created
in the current directory.
This error is issued if an non-existent directory is specified in the TMP
environment variable, or more than 26 concurrent compiles are taking place
in a multi-tasking environment and the directory in which the temporary
files are created is the same for all compilation processes.
.errnote SM-07 generation of browsing information failed
.pc
An error occurred during the generation of browsing information.
For example, a disk full condition encountered during the creation of the
browser module file will cause this message to be issued.
Browsing information is generated when the /db switch is specified.
.errtail
.errhead Structured Programming Features
.errnote SP-01 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.
.errnote SP-02 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.
.errnote SP-03 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'.
.errnote SP-04 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
.errnote SP-05 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.
.errnote SP-06 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.
.errnote SP-07 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.
.errnote SP-08 select structure requires at least one CASE statement
.pc
In the SELECT control structure, there must be at least one CASE
statement.
.errnote SP-09 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.
.errnote SP-10 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.
.errnote SP-11 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.
.errnote SP-12 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.
.errnote SP-13 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.
.errnote SP-14 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.
.errnote SP-15 attempted to use REMOTE BLOCK recursively
.pc
An attempt was made to execute a REMOTE BLOCK which was already
active.
.errnote SP-16 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.
.errnote SP-17 %s1 statement is not FORTRAN 77 standard
.pc
The statement %s1 is an extension to the FORTRAN 77 language.
.errnote SP-18 %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.
.errnote SP-19 %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.
.errnote SP-20 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.
.errnote SP-21 %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.
.errnote SP-22 no such field name found in structure %s1
.pc
A structure reference contained a field name that does not belong to the
specified structure.
.errnote SP-23 multiple definition of field name %s1
.pc
The field name %s1 has already been defined in a structure.
.errnote SP-24 structure %s1 has not been defined
.pc
An attempt has been made to declare a symbol of user-defined type %s1.
No structure definition for %s1 has occurred.
.errnote SP-25 structure %s1 has already been defined
.pc
The specified structure has already been defined as a structure.
.errnote SP-26 structure %s1 must contain at least one field
.pc
Structures must contain at least one field definition.
.errnote SP-27 recursion detected in definition of structure %s1
.pc
Structure %s1 has been defined recursively.
For example, it is illegal for structure X to contain a field that is itself
a structure named X.
.errnote SP-28 illegal use of structure %s1 containing union
.pc
Structures containing unions cannot be used in formatted I/O statements or
data initialized.
.errnote SP-29 allocatable arrays cannot be fields within structures
.pc
An allocatable array cannot appear as a field name within a structure
definition.
.errnote SP-30 an integer conditional expression is not FORTRAN 77 standard
.pc
A conditional expression is the expression that is evaluated and checked to
determine a path of execution.
A conditional expression can be found in an IF or WHILE statement.
FORTRAN 77 requires that the conditional expression be a logical expression.
As an extension, an integer expression is also allowed.
When an integer expression is used, it is converted to a logical expression
by comparing the value of the integer expression to zero.
.errnote SP-31 %s1 statement must be used within %s2 definition
.pc
The statement identified by %s1 must appear within a definition identified
by %s2.
.errtail
.errhead Subprograms
.errnote SR-01 name can only appear in an EXTERNAL statement once
.pc
A function/subroutine name appears more than once in an EXTERNAL
statement.
.errnote SR-02 character function %s1 may not be called since size w