Hi Elias and Peter,
first of all, I am planning to put the commands )LOAD, )SAVE, ... into a
separate
function. That will replace lines 72-132 in Command.cc by a call to a
new function.
The remaining lines cannot be broken down further - they are the "main
loop" of APL
Regarding terminal I/O
Well this is an opportunity to bring up something that has been on my mind for
some time.
My feeling is that a better way to deal with the I/O issue is to have an
abstract Class ( or Classes) from which
the various I/O implementations can inherit. e.g. Class Input, Class Output or
Class InputO
In the Android version that I have started working on, am I not going for a
plain text-based I/O model like the normal GNU APL session. This is because
terminal-oriented sessions are quite cumbersome to work with on a small
mobile device.
Instead, I intend to be a bit more clever when rendering re
