What about doing it the typical BASIC way: all DATA entries go in the same table, and you use the READ command to get the read the next cell, keeping an internal cursor that can be reset with CLEAR.
What Intybasic has is already better than that: You can set up multiple tables - use the command RESTORE tablename to set the internal cursor to the start of the specified table, and then use READ to get successive values from the table.
This works great if you use exactly one table at a time in your game. But I tend to write table driven code, with many different tables. For example, in Clowns and Balloons, I have one table that has the balloon positions for each round, and another table that describes the animation of the stretcher when hit. So I read the data for the first round, and the internal cursor is all set to read the next round's data, but then the clown hits the stretcher and I set the internal cursor to read the stretcher animation data, and so I "lose my place" in the balloon data.
What I want are read-only arrays of data, where I can index the data tables however I want, and can have more than one table active at a time.
I guess I haven't learned to think in the "typical BASIC way"...
Edited by catsfolly, Fri Feb 7, 2014 8:26 AM.