INPUT stack lift: 32S vs. 42S

[Dave Britten]

(10-19-2019 09:39 PM)Thomas Okken Wrote:  I think the behavior of INPUT makes sense in its own right, because it makes it easy to modify the existing value of the variable; getting pushed into Y means you can perform calculations on the original value without any preliminaries.

Ah yeah, that's an excellent point. Which makes it all the weirder that EDIT on a matrix doesn't behave this way! New entries overwrite X, and you need an ENTER first to operate on an element. Maybe it was easier to disable stack lift outright while editing, so the arrow keys wouldn't push the stack every time you moved through the matrix.