I wasn't referring to the management of APL memory, but rather native
memory used when calling functions through the FFI.
As an example, I've been recently working on integrating GSSAPI in Emacs
(I've previously integrated the same library in Common Lisp), and as an
example, let's take a look at a
Hi Alexey,
the output of eg. ⍎"COPY XXX.apl" is a string which can be
assigned or suppressed like this:
⊣⍎"COPY XXX.apl"
A ⎕COPY
would be behave exactly as ⍎")COPY ..." does, so just renaming ⍎")COPY ..."
to ⎕COPY
Hi Elias,
I understand. I recently had a look at how Erlang is building
their API to other libraries. Apparently they use an
opaque context in which all memory allocations they need are
recorded and the memory is freed when the context
is destroyed. T
Whether we use libffi or some hackish code, we need at least read, write,
malloc, and free.
Type can certainly be an argument to some of those functions.
I don't think it can be any simpler.
J supplies the foreign conjunction,
http://www.jsoftware.com/help/dictionary/dx015.htm
or in APL lingo, a
The main thing LIBFFI does is to provide a mechanism by which you can call
functions and pass parameters in the correct way without having to
hard-code information about the calling conventions of the platform you're
running on.
Suppose you have a pointer to a function with the following signature
Mac Pro 4,1 dual quad coe CPU’s, 6 GB ram running OS X 10.10.5 Yosemite, using
Terminal
I did a checkout of svn 884 and then configure with this
./configure MAKE_J=4 --with-libapl —with-android —
in order to see if it would use 4 cores….
Then did make and using Activity monitor I saw 4 instance
I believe passing/returning struct is actually compiler dependent (man gcc and
/struct-return).
What you are talking about implementation dependent type and alignment is a
real problem.
Actually without fully preprocessing the headerfiles, we can never be sure
about system/architecture dependen
On 10 February 2017 at 13:30, Xiao-Yong Jin wrote:
> I believe passing/returning struct is actually compiler dependent (man gcc
> and /struct-return).
>
In C++ it's compiler-dependent, I think. The C ABI however is stable in
this respect, at least on Linux.
> What you are talking about impleme
