WP 34S and 31S bugs and fixes

[Bit]

(12-08-2014 05:42 PM)walter b Wrote:  

(12-08-2014 05:19 PM)Bit Wrote:  This would still allow directly entering e.g. 1e-385 as 0.01e-383, which contradicts the rule "1e-383 is the smallest number that can be entered directly".

Correct. That can be only caught by range checking with the entire input closed. I understood that we can do that spending a few bytes (not that I assess that solution a perfect one - but it looks viable to me under the constraints given).

Alternative: we follow Nigel - but we don't have suitable error messages AFAICS.

d:-/

Walter, that problem can be very easily caught immediately during number entry, without spending any CPU cycles on converting the input into a floating point number. That check is practically free. The only question is if you'd prefer such a check to be performed.

And I'm happy to add a few extra error messages, it's really no effort. Let's try to figure out what's the best user interface and worry about coding later.