Calculator Community > Axe

More dynamic variables?

(1/3) > >>

johnbchron:
So I work in Axe, obviously (otherwise I would have put this in basic or some other topic), and I want to make large games. The main limitation I run into most of the time is that I don't seem to have enough non-final -- or for lack of a better word, dynamic -- variables. Does anybody have any ideas/solutions to this problem? I already know about A-Z, theta, and r1-r6, but are there any that I don't know of? Nobody else seems to have this problem.

Xeda112358:
A lot of people use the areas pointed to by L1~L6 to store additional data. If even those don't suffice (that's a lot of RAM) you could make a buffer/array stored in your program and store the data there, or for a really complicated method, create a temporary OS variable of whatever size you need  and store the data there.

Streetwalrus:
Xeda pretty much summed it up.
Note that I would not recommend creating buffers within your program, as most shells will write that data back to the actual program file and to archive when the program exits. That is in most cases not desirable: saving temporary data that you will erase later is wasteful, and you could end up with unpredictable initial state in your program because of that. In some cases you might want to use this for saving the game, but it's just better to make your own appvar for that.

Sorunome:

--- Quote from: Streetwalrus on March 14, 2018, 06:03:37 am ---[...]
That is in most cases not desirable: saving temporary data that you will erase later is wasteful, and you could end up with unpredictable initial state in your program because of that.
[...]

--- End quote ---
Hmmm couldn't you solve that in theory by clearing your temp. areas upon program start and upon program exit?

Xeda112358:
Yeah, that would actually work. It's still less efficient for the reason that it is taking up unnecessary memory, though.

Navigation

[0] Message Index

[#] Next page