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

[Claudio L.]

(03-02-2017 12:12 AM)rprosperi Wrote:  For ASN and STOKEYS, how about allowing both formats? Neither of these commands is time-sensitive, so the impact of determining which style (string or rc.p) to use (by peeking at the 2nd argument) will have no real effect other than to be more flexible. In such case, it's reasonable to require the full STOKEYS list use only 1 type of key code. RCLKEYS is less important (for me) so the default format of output (strings) is fine.

I can make ASN work with rc.p code (actually, it was renamed to ASNKEYS precisely because of the argument difference), but there's more to it: The string can represent more planes and key messages than rc.p code so using the old system you would miss out on some capabilities. Also, it requires a context number which indicates when the key definition is active, so you can have multiple definitions for the same key and key plane but to be used on different contexts (while at the stack, while in the command line editor, at the interactive stack, at a user custom form, etc.).
RCLKEYS and STOKEYS are means to backup/restore only, not for bulk editing of keys. The list format is internal and not meant to be edited by the user. No conversion or checks are happening during RCLKEYS/STOKEYS. Perhaps there should be a conversion to human readable string on RCLKEYS and reverse conversion on STOKEYS, but is not currently implemented.