[TI BASIC] Optimizing

Virtuoso · Post by **Virtuoso** » Tue 15 Mar, 2005 1:27 am

LX131(L)->T
LY131(L)->U
If LT31(L)=1

to

LX131(L->T
LY131(L->U
If 1=LT31(L

dysfunction · Post by **dysfunction** » Tue 15 Mar, 2005 12:48 pm

@DarkerLine: Thanks, that will at least shave off some size, though I don't think it will have much effect on speed...

DarkerLine · Post by **DarkerLine** » Wed 16 Mar, 2005 1:28 am

In the same way, you could shrink the first code you posted by almost 75%.

Virtuoso · Post by **Virtuoso** » Wed 16 Mar, 2005 1:37 am

consider using shorter list names also

dysfunction · Post by **dysfunction** » Wed 16 Mar, 2005 6:47 pm

@Virtuoso: Most of these optimiztions shave off only bery tiny amounts of code- I'll make these corrections later, since they make the code harder to read.

DarkerLine · Post by **DarkerLine** » Thu 17 Mar, 2005 12:43 am

There really isn't much you could shorten the list names.
You could use W31, X31, Y31, Z31 instead of X131, Y131, X231, Y231, but that only shrinks it by one byte.

Unless you wanted to make it completely arbitrary and incomprehensible by going L_AA, L_AB, L_AC, ... ,L_ZZ?

Guest · Post by **Guest** » Thu 17 Mar, 2005 2:47 am

All you gotta do is just remember shorter is faster

At least thats always been the case for me in BASIC.

Post by **tr1p1ea** » Thu 17 Mar, 2005 3:34 am

That isnt always the case, especially when there are loops involved. Often you get caught between making it smaller or making it faster.

dysfunction · Post by **dysfunction** » Thu 17 Mar, 2005 1:53 pm

Yes, this is large but fast.

DJ_O · Post by **DJ_O** » Thu 17 Mar, 2005 2:04 pm

Memory might not be a problem if you use Flash Gordon or such program. The code limit on the 83+ is 188229 bytes (in extended TI-BASIC language).

dysfunction · Post by **dysfunction** » Thu 17 Mar, 2005 9:52 pm

Yeah, I intend on using archive as much as possible. Zpic allows pics to be recalled directly from ROM, so I might not even need Flash Gordon.

Toaster · Post by **Toaster** » Thu 17 Mar, 2005 10:41 pm

When you call pics with zpic out of ROM they dont display right.

I wish there was some program that would call pics out of ROM but so far I have not found anything.

dysfunction · Post by **dysfunction** » Fri 18 Mar, 2005 1:04 pm

Actually, they do display right with ZPIC when called out of Archive.

MooK · Post by **MooK** » Wed 23 Mar, 2005 11:31 pm

Hi...I was wondering which would be faster for detecting whether or not an object was in the correct domain. I am not looking for size since this is a game written in basic, I will sacrifice space (since my game is turning out really small, my graphics for the sprites only take about 50 k

) for speed.
Example 1:
X+(X=0)-(X=95->X
Y+(Y=0)-(Y=63->Y

or Example 2:

If X=0:1->X
If Y=0:1->Y
If X=95:94->X
If Y=63:62->X

or maybe a combo of both? Example 3:

If X=0 or X=95:X+(X=0)-(X=95->X
If Y=0 or X=63:Y+(Y=0)-(Y=63->Y

I am just trying to avoid the extra restoring when X or Y is not out of range. Also, I use a modified version of the first example of code for changing my X and Y when a correct key is pressed, so for more speed would I change to whichever of the 3 types of code is fastest? Thank You.

DarkerLine · Post by **DarkerLine** » Thu 24 Mar, 2005 12:44 am

I'm pretty sure Example 1 is faster.

Code: Select all

X+(X=0)-(X=95->X 
Y+(Y=0)-(Y=63->Y

Except that you can optimize it to

Code: Select all

X+not(X)-(X=95->X
Y+not(Y)-(Y=63->Y