Re: TIB: G'day
[Prev][Next][Index][Thread]
Re: TIB: G'day
On Thu, 13 May 1999 11:07:31 EDT, Grant Winney wrote:
>
>>From: Jkhum98@aol.com
>
>(top of message not included)
>>that may be the problem, i dunno... on a related note, and something Ive
>>been
>>wondering in Basic, is that the programs gradually slow down upon
>>execution
>>for a while, and some games even get these memory errors after a while of
>>running. I was just thinking it is because the calc may be encountering
>>"Goto" statments within conditionals. For example, "If A=5: Then: B+1->B:
>>Goto D: End" and the program expects an "End" statement later on because
>>of
>>the "Then", but will never reach it. Im not sure how the calc handles
>>that,
>>but there must be some sort of Stack like there is in ASM which keeps
>>track
>>of all the conditionals. Say, if you put another "If:Then" statement
>>within
>>that conditional, it will then know to expect 2 "End" statements... After
>>a
>>period of time of jumping out of those statememts, maybe the allowed Ram
>>gets
>>full and we get a Memory Error. I cant think of anything else that would
>>do
>>this, or cause for a program to slow down like they do, but those are my
>>thoughts...
>>
>>Jason_K
>
>===================================================================
>
>I've noticed that too. If there is such a stack that these errors are
>building up in, I wish there was a way to clear it. I guess the only way
>around that right now is to train ourselves to not include a GOTO statement
>in an IF-THEN-END statement.
>
>-Grant Winney
>
Perhaps it's possible to have an ASM program that you run periodically that
clears the stack? That could be a possibility, but I still think that
Grant's right, just train yourself to not include GOTO commands from inside
loops.
James Vernon
jimbob_v@hotmail.com
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com