I hear you, but you can get the strings if you want them. Its
a fairly common trope in library code (OK, not equivalent to a
scripting language, but anyway) to have functions that return
a numerical code, accompanied by another function to convert
the code to a string if wanted. Also, with inbundle as it is
now, you can do a straight boolean test if you want, which you
could not do if it returned a string.
I agree with deleting the issscalar() function, and I think
the argument above is an important point in favor of accepting the
modified version of inbundle() and the new typestr() function.
--
Ignacio Diaz-Emparanza
DEPARTAMENTO DE ECONOMÍA APLICADA III (ECONOMETRÍA Y ESTADÍSTICA)
UPV/EHU Avda. Lehendakari Aguirre, 83 | 48015 BILBAO
T.: +34 946013732 | F.: +34 946013754
www.ehu.es/ignacio.diaz-emparanza/
www.ea3.ehu.es