Appendix
F:
Error
Messages 339
REDIM'D
ARRAY
An array name appears in more
than
one
DIM
statement. This error
also occurs if
an
array name
is
used (given a default size
of
11)
and later
appears in a
DIM
statement.
Place
DIM
statements near the beginning
ofthe
program. Check
to see that each
DIM
statement
is
executed only once.
DIM
must not
appear inside a
FOR-NEXT
loop
or
in a subroutine where either may
be executed more than once.
REDO
FROM
START
This
is
a diagnostic message during
an
INPUT
statement operation and
is
not a fatal error.
It
indicates that the wrong type
of
data (string for
numeric
or
vice versa) was entered in response
to
an
INPUT
request.
Reenter the correct type
of
data.
INPUT
will continue prompting
until
an
acceptable response
is
entered.
RETURN WITHOUT GOSUB
A RETURN statement was encountered without a previous matching
GOSUB statement being executed.
Insert a GOS
UB
statement
or
delete the
RETURN
statement. The
error may be caused by dropping into the subroutine code inadver-
tently.
In
this case, correct the program flow. An END
or
STOP
statement placed just ahead
of
the subroutine serves as a debugging aid.
STRING TOO LONG
An attempt was made by use
of
the concatenation operator
(+)
to create
a string longer than
255
characters.
Break the string into two
or
more shorter strings as part
of
the
program operation.
Use
the LEN function to check string lengths before
concatenating them.
SYNTAX
There
is
a syntax error in the line just entered (immediate mode) or
scanned for execution (program mode). This
is
the most common error
message.
It
is
caused by such things as misspellings, incorrect punctua-
tion, unmatched parentheses, and extraneous characters.
Examine the line carefully and make corrections. Note that syntax
errors in a program are diagnosed
at
run time, not
at
the time the lines
are entered from the keyboard. You can eliminate many syntax error
To Next Page
Loading...
