0 Members and 2 Guests are viewing this topic.
At school, we have to write these basic programs with terribly unoptimized code. I know there are situations where the use of Lbl and Goto is inevitable, but all of those programs use the Goto and Lbl commands as like there is no tomorrow.
Wow, I don't think I've ever used IS<(.
This topic reminds me how I was forced to use Goto to create loops on the TI-81 due to lack of While/Repeat/For()
0->ALbl LDISP "TRYA+1->AIf A<100ThenGoto LEnd
Quote from: DJ_O on February 22, 2011, 11:01:13 pmThis topic reminds me how I was forced to use Goto to create loops on the TI-81 due to lack of While/Repeat/For() Like:Code: [Select]0->ALbl LDISP "TRYA+1->AIf A<100ThenGoto LEndStuff like this?
I love Java's break statement. It changed my life. Before, I would just goto out of the loop.
Quote from: graphmastur on August 09, 2010, 08:31:01 pmI love Java's break statement. It changed my life. Before, I would just goto out of the loop.++
Casio doesn't have repeat, so it's almost nessecary to have goto to restart the loop from several conditional statements inside of the loop without causing an error (which it will if you use Do-LpWhile or While-WhileEnd
Quote from: Scout on February 24, 2011, 12:28:13 pmQuote from: DJ_O on February 22, 2011, 11:01:13 pmThis topic reminds me how I was forced to use Goto to create loops on the TI-81 due to lack of While/Repeat/For() Like:Code: [Select]0->ALbl LDISP "TRYA+1->AIf A<100ThenGoto LEndStuff like this?Probably with IS>(, I'd imagine.
Lbl 1DoGoto 1
Is that really a memory leak, though? You're telling the OS to continually allocate memory for Do statements. It's nothing more than infinite nesting. From what I understand, memory leaks are bugs in the code where the interpreter doesn't properly handle the memory allocations. Your example wouldn't count unless that program somehow terminates earlier than it should.