Optimized Stack Operations

[Paul Dale]

(02-25-2019 06:35 AM)deetee Wrote:  every operation costs 2 bytes of flash memory

Do you have more than 256 operations defined?
That's a lot for a small memory device.

If there are more operations than this, they could be packed. Two twelve bit codes per three bytes e.g. This could save a fair bit of flash.


As for stack operations, it might be worth implementing a few extra ones natively. The shuffle on the WP 34S is very handy, it allows any combination of the first four stack levels to be rearranged, duplicated and dropped. I suspect you'll not have space for quite as rich a command, but something might be possible. Two bits could specify the top four levels as a PICK. Four bits could function as two picks from the top four levels.


Pauli