Kevin wrote:I'm not complaining about BASIC is limited I'm just saying that we dont have enough vars
ain't that the truth...and making an rpg in BASIC is a pain...*mutters* I'll be posting my code up here soon to see if anyone has any suggestions for optimizing...because I KNOW it sucks..lol
DarkerLine wrote:Still, if you ever feel like you're running out of variables in Basic, then Asm is not for you.
Huh? If you're running out of variables in BASIC, then shouldn't you turn to assembly? You can have as many "variables" as you want in assembly (RAM permitting)
"If SOURCE is outlawed, only outlaws will have SOURCE."
Well storing stuff in ram for safekeeping and being able to perform operations with data in asm are 2 different things. Sure you can store 'variables' but you can only perform operations with the data using the registers. And also considering that this is an ACC based system ...
You can store as much stuff in memory as you want in basic too ... just keep stuff in lists etc.
"My world is Black & White. But if I blink fast enough, I see it in Grayscale."
I've still got about 5-6 variables left to use (out of the A-Z, theta set) for in-game play in Tankies. So yeah, no problems there.. no list use except for option lookup.
There's also the finance variables, stat vars if you can figure out how to store to them (it's complicated), unused window boundaries (Tmin, Tmax, thetamin, thetamax, etc.), even USED window boundaries if you don't use the graph screen (just remember to fix them afterwards), table variables (TblInput is a 7-element list), etc.