NSB8 Datasheet, PDF (140/158 Pages) List of Unclassifed Manufacturers – BASIC interpreter for Z80 family

grifo^®
ITALIAN TECHNOLOGY
NO PROGRAM ERROR
(non trappable)
This error occurs when an attempt is made to RUN and there is no current program.
NUMERIC OV ERROR
(4)
This error occurs whenever an arithmetic operation results in a number larger than
9.9999999E+62. Numbers larger than this cannot be represented in standard versions of
NSB8. (Numbers smaller than 1E-64 are converted to 0).
OUT OF BOUNDS ERROR
(3)
This message occurs when a numeric argument is not within legal range, e.g., when an array subscript
is too large or too small, or when an argument used with CALL, EXAM, FILL, INP, or OUT is not
in the correct range. When dealing with diskette files, an OUT OF BOUNDS ERROR will occur as
attempts are made to READ from or WRITE to a file beyond its absolute end (determined by the file
size).
READ ERROR
(11)
When using the READ statement, if an attempt is made to READ a numeric value into a string
variable or vice versa, or to READ any value when there is no more DATA available, a
READ ERROR will occur.
STOP
(15)
This is not really an error, but when <control-C> is enabled and pressed while an ERRSET statement
is in effect, the attempted program interruption is treated as a program error, with 15 as its code. In
other words, error 15 means that <control-C> was pressed while ERRSET is in effect.
SYNTAX ERROR
(10)
This is the most commonly generated error message. It occurs when a language feature has been used
improperly, or has been improperly formed (typed incorrectly). Most of these mistakes become
obvious upon brief (but careful) examination of the faulty command or statement (as compared with
its manual description). Refer to the appropriate exposition or DISCUSSION section to determine
the correct form of the language feature in question, and make sure that all keywords are correctly
spelled.
TOO LARGE OR NO PROGRAM ERROR (non trappable)
This message occurs when an attempt is made to LOAD, APPEND, or CHAIN to a program which
either is too large to fit in the program/data area, or is not a valid BASIC program.
TYPE ERROR
(4)
TYPE ERRORs happen when a string value appears where a numeric value is expected, or vice
versa. With regard to disk file operations, an attempt to OPEN a file whose actual type doesn’t agree
with the type specified in the program, or to READ a value on disk into a program variable of the
wrong type, will lead to this error.
Page 128
NSB8
Rel. 5.10