Hi Peter,
good question, I'm really happy to explain it.
GNU APL is almost completely Doxygen documented. Almost conmpletely
means that new functions
take a while before I update the Doxygen documentation (it makes little
sense to do that while functions
come and go).
Doxygen is a terrific t
Hi Peter,
the current line editor of GNU APL is in Nabla.cc. It is pretty simple.
The editor gets its line input from Input::get_user_line_nabla().
My concern with [a?b] is this: currently we print a prompt and then get
a user line
from either readline or from the operating system (in cooked m
Peter,
The Emacs mode is much more than a simple way of editing functions in an
editor. The intention is to transform the standalone GNU APL interpreter
into some kind of IDE in a similar way as SLIME does for Common Lisp. The
Emacs mode backend provides similar functionality as the Swank backend
Hi Elias:
Firstly I am totally agnostic as to which text editor should be used.
I don't even understand why there should be an Emacs mode.
But since you said it's actually generic maybe we can change it's name
to more clearly reflect its generic nature? External Editor Mode? Just a
fleeting th
Hello Peter,
You might want to read up in the email archives on the discussions that led
to the creation of the Emacs backend. It was done exactly because Jürgen
did not want to maintain a special protocol used for things such as the
Emacs mode.
It's included in the base release because shipping
Hi Jürgen - I'm back from a mini-break.
The ISO Standard Ch 16 p 239 et seq specifically states
"The user makes entries on a keyboard, and obtains responses by seeing them
presented on a display- device. The combination of a keyboard and a
display-device is intended to represent, abstractly, a te
