WP 34S and 31S bugs and fixes

[Bit]

(01-12-2015 02:31 AM)Paul Dale Wrote:  

(01-12-2015 02:00 AM)Bit Wrote:  Another option is to save the stack only when invoked directly by the user (not from a program). That's when the convenience of not losing the stack matters the most, and that's when using some extra temporary registers is least likely to be a problem.

It is also inconsistent which won't please Walter


- Pauli

AFAICS work on the WP 34S has very much been about finding the best compromises to bring the most out of the very limited hardware, and some of those compromises are by necessity not pretty but useful. I suppose the pros and cons of saving the stack will need to be carefully considered.

Can you or anyone estimate how likely it is that we'd run into problems if the mentioned functions always saved the stack?