RE: A85: PRogramming
[Prev][Next][Index][Thread]
RE: A85: PRogramming
Write down where the bug is, and work on other parts of the program. When
you have them finished, then go back to the bug. It'll help clear your
mind.
Nathan
-----
Stuntman (Nathan Haines) - ICQ UIN#: 2157863
http://table.jps.net/~stuntman/nathan.html
QuickBASIC/Visual BASIC/TI-BASIC programmer (just your basic programmer)
President of Stuntworks - http://www.jps.net/stuntman/
> -----Original Message-----
> From: owner-assembly-85@lists.ticalc.org
> [mailto:owner-assembly-85@lists.ticalc.org]On Behalf Of Kaus
> Sent: Thursday, December 17, 1998 7:49 PM
> To: assembly-85@lists.ticalc.org
> Subject: A85: PRogramming
>
>
>
> I have an interesting problem. I have a program (or a part of one) that i
> made that has an error. Now, this error is of LOCK material, but its
> occurances are almost random, and the type of LOCK is similarily so.
> The first time I testing the program, the calculator had tons of
> games and
> stuff on it and the test program. Running the test program, I
> was checking
> for bugs. Its a menu scrolling program, and everything seemed to work
> fine. I went to the bottom line in the menu, and held down the down
> button, to check my lower bounds code. IT worked for a long long time.
> Then, The entire bottom line went screwy and it locked.
> I reset it and got a backup of the calc before i had even put the test
> program on it, and then reput the test program on and tried it
> again. Same
> results.
> Then i reset it and put only Usgard and the test program on. This time I
> wnet into the test program and the calc locked as before, but i didnt even
> have to press anything eyt.
> So, i reset it again, put the minimal Usgard and test program like before
> and tried again. thsi time, it never locked. So, I reset it and put all
> the games, etc. stuff back on it with the test program, like i had the 1st
> two times. I tried again, and it worked for a long long long time, but
> hten it locked again, but it was a different type of lock than before.
> I tried it again witht eh same scenario, and this time it took a long long
> long time to lock, but this time it was back to the way it had before.
>
> So, it locks inconsistantly and alsmot randomly. In the course of the
> program, I dont see any possible reasone they would press down that many
> times, or hold it donw or anything in the menu, and so the users shouldnt
> encounter the bug. But, I would like to fix it eventually (sucks to have
> buggy code, ya know?) but the rest of the program needs to get a move on.
> Should I jsut leave it as is, use it, and see if any problems occur?
> Should I spend even more time trying to fix it now?
> Either way had pluses/negatives, so its up for grabs. Just trying to get
> some input from other programmers in the comunity.
>
> Kaus
>
>
References: