good to hear that init_libapl solved most of your problems.
Regarding ∇: it is the same story as for )COPY.
You could think of the apl interpreter binary as being
libapl with an interactive stdio fontend:
╔═══ apl interpreter ═══╗
║ ║
║ ┌── stdio ──────────┐ ║
║ │ │ ║
║ │ cin / cout / cerr │ ║
║ └───────────────────┘ ║
║ ║
║ ┌── libapl ─────────┐ ║
║ │ │ ║
║ └───────────────────┘ ║
╚═══════════════════════╝
Using libapl with other languages like python or erlang simply
replaces the stdio frontend with the other language. The interpreter
reads line by line from the frontend and processes it (aka. REPL).
The ∇-editor uses, in principle, the same interface to the frontend,
but it may pull a line rather than a line being pushed into it. I dont
quite remember the details since this works for a long time now. But
I believe the ∇-editor may have its own REPL loop.
I should also mention some callbacks that you may set. Elias
Mårtenson has written a GNU emacs integration for GNU many
years ago, maybe you want to have a look at it as well.
Best Regards,
Jürgen
On 6/12/22 2:38 AM, enz...@gmx.com
wrote:
Hi Sorry - using init_libapl cleared up all the libapl fpc coding problems (i failed to uncomment the relevant code first time i tried it) except using )copy (my copy procedure simulates it though) and trying to create a fns apl_exec('∇w');maybe i am using wrong syntax trying to create a fns one line at a time thanks enztec
