Problems with EQUALALL on RDTABLE, TERMTABLE
... the READTABLEP test and maybe the TERMTABLEP test in EQUALALL are bogus, left over from Ascii days. I think it should work properly if those specific tests are removed, just letting it fall through the GETDESCRIPTOR (unless there are internal structures like alists or proplists where order is not defined).
Should READTABLE and TERMTABLE be set up to allow non-ASCII entries?
The READTABLEP datatype declaration itself is suspicious. It looks like it is set up for a 24-bit pointer world, padding out the high-order byte of pointer fields. I also leave this for some other time.
in a d atatype it does packing. EQUALALL goes back to Interlisp-10.
Originally posted by @rmkaplan in https://github.com/Interlisp/medley/issues/1480#issuecomment-1873683220