That's your opinion.. IMO, you can hardly afford not to optimize every byte/tstate on such a limited system as our TI's. Of course you can over do it, but I have time enough to waste on a keyscanner.
Note though that I didn't initially optimize it, I just wrote it to do what it was supposed to do.
Oh and rotating isn't any faster than shifting unless you do it with A which in impossible ( =would hurt the code too much ) here.
[TI-ASM] key scanner with low values
Moderator: MaxCoderz Staff
- driesguldolf
- Extreme Poster
- Posts: 395
- Joined: Thu 17 May, 2007 4:49 pm
- Location: $4080
- Contact:
Well, I said I didn't completely read it, did I?King Harold wrote:Oh and rotating isn't any faster than shifting unless you do it with A which in impossible ( =would hurt the code too much ) here.
To avoid misunderstandings:
Anyway, I meant that you should always optimize, but if you have to choose between speed and size, then choose wisely (depending on the situation):
In loading screens, menu's and stuff: I would optimize for size (and speed if possible without making the code unreadible like Spencer says)
In a costum grayscale program, loops within loops within loops and so on, I would optimize for speed (and size if possible, but speed has priority)
Wich you all do of course