I have no idea how to read anybody's optimized code.

Forum Attachments

Summary:

I need some tips and pointers in layman's terms.

I have no idea how to read anybody's optimized code.

BShtterman01 05 Sep 2023 17:11

I'm not exactly new to coding the TI-84+, but I'm pretty damn new to optimizing my code. I've got the most messy and untamed programs with the most illegible and run-on code within it, and I have no clue how to fix any of it. If somebody could give me optimization tips and explain them like I'm 5 years old that would be wonderful.

Thanks!

Last edited on 05 Sep 2023 17:13 by BShtterman01 Show more

Re: I have no idea how to read anybody's optimized code.

jonbush 06 Sep 2023 03:13

Generally when we talk about optimization here, we are concerned with using the fewest number of tokens to accomplish the desired task (code golf). Fortunately, TI-Basic has many commands that combine several operations into one line. Review the Command Index to see if there is a command to do what you want. For instance, if you want to add up the numbers in a list, you might initially write code like this:

0->I
0->A
While I<dim(L1
I+1->I
A+L1(I)->A
End

This can be simplified to:

sum(L1->A

• You may also be able to use Piecewise Expressions to simplify conditional code to a single line.
• Applying already optimized Routines can also help.
• Ultimately, optimizing code often requires several iterations of trying different things before settling on an acceptable solution.
• To make your code easier to understand, you should generally avoid the use of Goto and Lbl, which can make tracing the code execution very difficult. Reducing the amount of nesting within your code will also help.
• Reduce duplicate code. Duplicate code makes implementing improvements difficult since you have to make changes in many places. For complex programs, like games, using a Finite State Machine (FSM) structure can help you reduce duplicate code without the use of Goto.
• Editing your code on a computer with a program like SourceCoder on Cemetech, or TI Connect CE. This will make programming much faster and allow you to see larger sections of code at the same time. SC also supports indentation, which makes it easier to keep track of nested code.

Re: I have no idea how to read anybody's optimized code.

unformatted 10 Nov 2023 17:33

If you are avoiding the use of Goto and Lbl, then how do you not just have to put the same line of code every time? If for instance I wanted to delete my variables after using them, then I could just add this. Especially if you are using a Menu beforehand to go to different code functions, then wouldn't this be especially necessary?

code here bla bla
goto 1
Lbl 1
DelVar insert variables hereDelVar insert variables hereDelVar insert variables hereDelVar insert variables here

Re: I have no idea how to read anybody's optimized code.

jonbush 12 Nov 2023 23:53

There are certain cases where using Goto and Lbl may be necessary, but there are usually alternatives (except for when using Menu().

For instance, you could just place your cleanup code at the end of your program so that it will always run after the program control flow exits. Example:

0→E  // exit code
0→S  // program state
Repeat E
// Code that executes every loop goes here

If S=0  // case 0
Then
Prompt B
If B=3
1→S
End
If S=1  // case 1
Then
Disp "EXITING NOW
1→E
End
End
// Cleanup code here
DelVar EDelVar SDelVar B

This is a simple implementation of a finite-state machine, which allows you to jump between different blocks of code ("states") based on transition conditions. The main loop runs continuously until the exit variable (E in this case) is set, and executes the code in the current state (S). This structure allows you to effectively re-use sections of code without Gotos.