newRPL: [UPDATED April 27-2017] Firmware for testing available for download

[Claudio L.]

Also fixed on this version (updated 02/07/17):
* EVAL on lists changed behavior: now it EVAL's every element instead of exploding the list. This is necessary for the next item.
* Symbolic operations with lists and matrices was fixed:

While you can't directly type a vector or matrix or list inside a symbolic (same as 50g), any variable in a formula may contain a matrix or a list and operations will be carried through as expected.
On the 50g, using lists in formulas was limited because of the '+' vs ADD, and the behavior of EVAL. In newRPL you can use lists to do simultaneous evaluation of multiple points in a function for example. If more than one variable has lists, the lists must have compatible dimensions to operate element-by-element.

* Numeric auto-simplification issues were fixed and improved.
* ->Q no longer returns fractions in the form 'N/1'
* Symbolic numbers stay symbolic after EVAL. This is a change in behavior necessary to prevent the loss of symbolic information during sequences of operations like inverting a matrix. Without this fix, for example a symbolic pivot '1/2' was being inverted to 2 (not '2'), and then used in a division in row-operations. Then an element of 1 would be divided by 2 instead of '2', returning 0.5 instead of the expected '1/2'.

* Command ULIST was added to list custom units per post in this thread.
* When a block of objects is defined in the interactive stack:
Right Cursor = COPY to current location
Left cursor = MOVE to current location
It was reversed from my previous post for consistency as PASTE feels more like COPY.
* Fixed symbolic numbers vanishing during ->NUM.
* Adds a bitmap cache to the stack display, making it faster (needed to speedup the interactive stack)
* The TYPE command was implemented (type numbers are different from 50g). Also added TYPEE (extended), which provides more information about the object (depending on type). For example for numeric types, TYPEE returns XX.MN, where XX=object type (=10 for numbers), M=digit that changes with the base the integer is in (1=decimal), N=digit that has certain flags: 1=APPROX. NUMBER, 2=EXACT INTEGER, 3=APPROX. INTEGER
So an exact integer in decimal base will return 10.12,while TYPE would return only 10.
Some objects don't have this extended information yet, will have it soon (for instance, an angle should tell you if it's in DEG/GRAD/RAD/DMS, etc., a matrix should say if it contains any complex numbers or symbolic items).