A.1 Compile-Time Errors
BASIC diagnoses compile-time errors and does the following:
.
Indicates the program line that generated the error or
errors.
.
Displays this program line.
.
Shows you the location of the error or errors and assigns
a number to each location for future reference.
.
Displays the mnemonic, statement number within the
line, the location number as previously displayed, and the
message text. This is repeated for each error in the line.
BASIC repeats this procedure for each error diagnosed dur-
ing compilation. The error message format for compile-time
errors is as follows:
%BASIC-<l>-<mnemonic>, <n>: <message>
<l>
Is a letter indicating the severity of the error. The severity
indicator can be one of the following:
.
I - indicating information
.
W - indicating a warning
.
E - indicating an error
.
F - indicating a severe error
<mnemonic>
Is a 3- to 9-character string that identifies the error. Error
messages in this appendix are alphabetized by this mnemonic.
<n>:
Is the n th error within the line's picture.
<message>
Is the text of the error message.
For example:
Diagnostic on source line 1, listing line 1, BASIC line 10
10 DECLARE REAL BYTE A, A
........................1.......2
%BASIC--E--CONDATSPC, 1: conflicting data type specifications
%BASIC--E--ILLMULDEF, 2: illegal multiple definition of name A
This display tells you that two errors were detected on line
10; BASIC displays the line containing the error, then prints
a picture showing you where the errors were detected. In the
example, the picture shows a 1 under the keyword BYTE and
a 2 under the second occurrence of variable A. The following
line shows you:
.
The error mnemonic CONDATSPC
.
Which error in the line's picture is referred to by the
mnemonic
.
The message associated with that error
In this case, the error message tells you that there are two
contradictory data-type keywords in the statement. The next
line shows you the same type of information for the second
error; in this case, the compiler detected multiple declarations
of variable A.
If a compilation causes an error of severity I or W, the
compilation continues and produces an object module. If a
compilation causes an error of severity E, the compilation
continues but produces no object module. If a compila-
tion causes an error of severity F, the compilation aborts
immediately.
The following is an alphabetized list of compilation error
messages: