Maybe running different environments/calc states will be preferable for any label caused issues? When at sea I seldom do any cost calculations or civil engineering. And even if this might happen with a probability 1:20^6, switching from one state to another isn't a big thing - provided that my landf...
Don't ask for [RPN] readability without thorough documentation after one year (if that long), if your code gets larger, for instance to calculate cost proposals. But you can code q'n'd. While this is true, in the case of RPL it's more like one week... :lol: Still, I like them both. Boy ... and I wo...
Some aspects of the RPNs appear not logic to me: flags and registers. SF 01 or STO 99 should be notated as 1 SF or 99 STO. That's a matter of getting used to it -- I've got the opposite problem with RPL (99 STO should be notated as STO 99) ;) Sure it is, and after approx 35 years I think I am ;) On...
Some aspects of the RPNs appear not logic to me: flags and registers.
SF 01 or STO 99 should be notated as 1 SF or 99 STO. This would need a fifth stack level to keep the four level stack as we know it.
But for the rest i'm happy with the small calculators.
A faster refresh rate would be great - if this isn't an issue with the calculators clockspeed, but 24 MHz should be sufficient. A larger font size also would be nice since it isn't a pleasure to work with such small numbers. Simple arithmetics isn't really such a big thing for such a calculator - es...
I always wondered "What to do with the large display?". So I had the idea of using it like a printer calculator. Right now it's capable of simple arithmetics (+ - * /), but no exponents - plus former results can be recalled via up and down keys (depth of 9 results plus enter line). It's ex...