All, I found the problem. The last statement on the line was MAXFILES=2 (10 DEFINT B-D,P:P(65):MAXFILES=2)
Apparently Radio Shack neglected to mention that setting MAXFILES clears the BASIC RAM area upon execution. All variables are cleared, strings set to NULL, DEF statements negated and array indexes returned to maximum of 10. Sorry for any panic caused! Regards, Peter On Sat, Jan 13, 2018 at 7:10 PM, Peter Noeth <[email protected]> wrote: > All, > > Is it just me, or has anyone else had problems with M100 numeric arrays. > I wanted to use a numeric array on my M102, but I keep getting a BS (Bad > Subscript) when trying to access indexes over 10 on a single dimensioned > array. > > BASIC does not complain about DIM P(65) or DIM P%(65), but P(11)=22 > gives a BS error. The book says arrays can be whatever size/dimensions that > memory will allow, but only seems to accept indexes 0-10. The examples only > use 10 as the index. > > Is this another one of the documentation oversights? I don't remember > reading about problems with this computer was in popular use. > > String arrays don't seem to have this problem, at least for singly > dimensioned arrays anyway. > > I guess I could set HIMEM and manipulate the array myself. > > > Regards, > > Peter >
