Re: TIB: G'day

To: ti-basic@lists.ticalc.org
Subject: Re: TIB: G'day
From: "Grant Winney" <cosmo70@hotmail.com>
Date: Thu, 13 May 1999 11:07:31 EDT
Delivered-To: ti-basic-outgoing@towerguard.unix.edu.sollentuna.se
Delivered-To: ti-basic@lists.ticalc.org
Reply-To: ti-basic@lists.ticalc.org


>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


_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com

Follow-Ups:

Re: TIB: G'day

From: "Miles Raymond" <m_rayman@bigfoot.com>