ally, but I don't know.
>
> I should mention that libapl is mainly a work of Dirk Laurie, I suppose he
> does not use dlopen(), but uses approach 1.
> Maybe Dirk can give you some more hints about how to use libapl.
I did this three years ago, using SVN 570 of GNU APL. In an ideal
world
Hi Jürgen:
a←1
a←{⍺*⍵}
SYNTAX ERROR
Also:
f←{⍺-⍵}
f←1
SYNTAX ERROR
Would it be possible to print NAME CLASS ERROR instead?
Best wishes
Dirk
2015-02-22 21:48 GMT+02:00 Dirk Laurie :
> The folllowing program pinpoints what I do not understand about
> the use of Value and Value_P.
I am beginning to think it may be a bug. Here is a minimal example
of the phenomenon that causes it.
~~~
#include
using namespace std;
#include
Current:
/// debug-print \b this value
void debug(const char * info);
Suggested:
/// debug-print \b this value under \b info
void debug(const char * info) const;
Hi Jürgen:
I've got code that works except for bugs unconnected with the GNU APL
routines.
I decided to implement the interface as a wrapper for an item of type
`const Value_P&`. API.cc contains the following lines:
// The commented-out variants give segmentation errors, I don't understand why.
Hi Jurgen:
I have observed that:
1. All commands except )ERASE and )HELP honour the `out` parameter.
2. )HELP writes "Commands are:" to `out`, which is always CERR, the
built-in commands directly to CERR, and user-defined commands to
`out`, which is always CERR.
There seem to be hidden mysteries
If you type Ctrl-D, you are told to use )off.
If you then type )off, the message
EOF at Command.cc:68
is issued. You need another )off to leave APL.
APL 1.4 quits at the first )off.
Is this difference intended?
Hi Jurgen:
Since merely loading libapl.so (which is all of GNU APL except main.o)
creates an APL workspace, the question of clean termination arises.
I have experimentally determined that )OFF does not call finalizers
on the Lua side. This is unacceptable, since Lua provides a facility
for progra
2015-01-30 12:57 GMT+02:00 Elias Mårtenson :
> I already do pretty much this in the Android version. The Android APK
> contains libapl.so which is then linked from the Java code which drives the
> user interface.
>
> Building libapl.so takes a bit of manual work right now, but in essence I
> config
a library that would allow the embedding of APL functionality in
a different host program?
Thanks for a very impressive APL implementation, and best wishes.
Dirk Laurie
10 matches
Mail list logo
