You will recieve a memory error in any of the following instances:
1) You create a loop and within that loop, you Goto out of it alot.
2) You create a loop with Lbl/Goto and are using the Goto command inside of an If:Then End statement.
3) You call a program, then that program calls the parent program (The one that called it)
The reason you recieve such errors is because:
1A & 2A) The calculator stores to RAM everytime it reaches an If:Then command structure. Basically, the calc sees If A=1:Then it does this: End+1->End. (Not actual, just an example) And this takes up RAM. If it is done very frequently, then the memory will dissappear very quickly. Quitting the program will reset that "variable" You will also notice that in your game/program that it lags after some use, this is the reason.
3A) The calc also keeps track of which program calls another program by nearly the same means, but also takes up a little more memory, because it needs to keep track of stuff more. If you are always just calling programs, and never using Return, you will eat up the memory VERY quickly.
Anything I missed?
1) You create a loop and within that loop, you Goto out of it alot.
2) You create a loop with Lbl/Goto and are using the Goto command inside of an If:Then End statement.
3) You call a program, then that program calls the parent program (The one that called it)
The reason you recieve such errors is because:
1A & 2A) The calculator stores to RAM everytime it reaches an If:Then command structure. Basically, the calc sees If A=1:Then it does this: End+1->End. (Not actual, just an example) And this takes up RAM. If it is done very frequently, then the memory will dissappear very quickly. Quitting the program will reset that "variable" You will also notice that in your game/program that it lags after some use, this is the reason.
3A) The calc also keeps track of which program calls another program by nearly the same means, but also takes up a little more memory, because it needs to keep track of stuff more. If you are always just calling programs, and never using Return, you will eat up the memory VERY quickly.
Anything I missed?