how to shrink code

[tenaja]

Peter, it depends on the location of the LookUp statement in your program.

Just do a little experiment by changing its location in the program.

A lot also has to do with how many elements you are looking up. It does not pay off until you are looking up more than just a few... 2-3, and it is a waste; a dozen and it saves a lot.

[mister_e]

I tend to use internal EEPROM for that when at all possible.

If you want how nasty we could shrink it... challenge us a little bit and post it here

Who take he challenge? Darrel? Bruce? Melanie? Alain? Skimask? Anyone?

[skimask]

I tend to use internal EEPROM for that when at all possible.
If you want how nasty we could shrink it... challenge us a little bit and post it here
Who take he challenge? Darrel? Bruce? Melanie? Alain? Skimask? Anyone?

I'm up...but I'm afraid all I'll get is spanked...

[sayzer]

I tend to use internal EEPROM for that when at all possible.

If you want how nasty we could shrink it... challenge us a little bit and post it here

Who take he challenge? Darrel? Bruce? Melanie? Alain? Skimask? Anyone?

Steve,

Do you mean a scan routine that will get an input variable, then scan EEPROM and provide an output variable?

________________________________

[mister_e]

depending which part of the message you refer. But yeah, when possible i replace LOOKUP by a READ ... depending what also on-board i may use an external EEPROM. I don't have any conventions. Since awhile all my projects are different. I just try to find the best compromise to reduce cost, pcb space etc etc.

Code shrinking is a kind of funny challenge... Peter says he already shrink it and maybe he's still working on, i don't know. What i suggest to him, is to post his whole code here to see how much we could reduce it.

Not a must, be as i said, that's fun. I know Darrel like that kind of thing