No.
o
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
50
51
52
53
70
71
73
74
75
76
77
78
80
90
91
93
94
100
101
103
104
105
Message
no
error
command
not
recognized
end
of
statement
expected
variable
name
expected
unrecognized
print
item
wrong
data
type
numeric
expression
expected
string
expression
expected
variable
not
found
variable
undefined
missing
separator
name
too
long
duplicate
name
string
literal
expected
mi
ss
i ng
endproc
bad
proc
statement
premature
end
of
statement
program
structure
fault
too
many
numbers
missing
closing
quote
mi
ssing
exponent
after
liE"
number
too
bi
g
unknown symbo l
evaluator
syntax
error
mismatched
parenthesis
type
mi
smatch
wrong
number
of
arguments
string
too
long
dlvide
by
zero
bad
function
arguments
string
subscript
error
out
of
memory
no room
to
open
a
fi
le
incomplete
fi
le
transfer
out
of
range
file
not
open
cannot
open
file
write
to
read
only
fi
le
wrong
file
type
bad
fi
le
name
error
reading
fi
le
Example
apend
let
x=3
let
y=4
let
31=x
print
create
•
(1)
let
x="fred"
let
x$=4
let
x=qq
(qq undefined)
prj
nt
qq
print
at
5
let
thisverylongname=4
create:n$:n$:endcreate
(2)
•
(3)
•
(3)
createl/test":endcreate
•
(4)
•
(5)
let
x$="f
red
let
x=1.2E
let
x=1.2E100
let
x=%
let
x=3+
let
x=(3+5)
/7>
let
x$=
lI
fred"+3
let
x$=str(1,2)
let
x$=rept
("*",256)
let
a=O:
let
x=5/a
let
x$=sqr(-4)
let
x$="fred"
(to
97)
(6)
•
(7)
•
(8)
print
at
100,100;37
append
(without
tirst
opening a
file)
loa
k
"x
xx"
(non-existent)
look
II
n
ames":
insert
s
load"names
ll
(data
file)
save"3test"
•
(9)
Reference
1)
The most likely cause of error 5 - 'wrong data type" -
is
that you have inputted Notes
text
when a number
is
expected,
e.g.
in
response
to
an input statement such
as:
;
nput
X
2)
Error
13
- "string literal expected" - can occur,
for
example, during the import
of a
file
that you have constructed yourself (without using any of the export
commands
in
the OL programs).
If
means that Archive has found a numbe( or
a numeric or fext expression, where
it
was expecting
to
find a literal text
value.
In
mosf situations where Archive finds numeric data when expecting
text,
or vice
versa,
It
will give error 7 or error
8.
3) Errors
14
- "missing endproc" - and
15
- "bad proc statement" - should never
occur
in
normal
use.
They Indicate that Archive has detected a missing endproc
or an error
In
the structure of a proc statement
In
a procedure. They are only
I'lkely
to
occur if you construct a program
file
with an editor other than the one included
in
Archive.
4)
Error
17
- "program structure fault" - usually indicates that an all, if or while
is
not paired with a corresponding endall, endif or endwhile
in
a procedure.
You
12/84 53
To Next Page
Loading...
Need help?
General
