Hi,
apl is NOT depending on libapl. libapl is essentially apl but with a
different API
as defined in libapl.h. But a number of object files differ and
therefore you cannot
simply build libapl and link it with apl.
On 6/20/21 11:59 PM, enz...@gmx.com wrote:
Hi
Jürgen - thanks for fixing the
As to your test file, you
should use g++ instead of gcc.
On my box the following:
// compile with: g++ -o test test.c -L
/usr/local/lib/apl -lapl
#include
#include
#include
int main (int argc, char * argv[])
Hi,
you should be aware that ]PUSHFILE puts you into a new
immediate
execution context, just like an error does in normal APL
execution.
Unlike the immediate execution after an APL error, you cannot or
should not leave it with → or →N but only
