[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Further on MEX
From: |
Aravindh Krishnamoorthy |
Subject: |
Re: Further on MEX |
Date: |
Mon, 5 Jan 2009 23:46:05 +0530 |
Dear Michael,
You're pointing to: libffi. BSD licensed libffi can handle calls +
parameter passing. Thanks.
Also, of course, we'd like to restrict the shared-object's to the
respective platform: Linux .so's from Linux, Windows .DLLs from
Windows. Sensible?
Also, Matlab requires a header file (with c-signatures) to be passed
during 'loadlibrary' call which is parsed using perl (best I can
remember.) ATM, I don't know how we mirror that to Octave.
Yours sincerely,
Aravindh
2009/1/5 Michael Goffioul <address@hidden>:
> On Sun, Jan 4, 2009 at 9:57 AM, Aravindh Krishnamoorthy
> <address@hidden> wrote:
>> 3. [feature-req] What is the take on supporting 'loadlibrary', etc
>> functions in Octave?
>
> Calling a foreign function in binary form (that is, without a compilation
> step) will inevitably involve some assembly coding and will be
> processor specific. I've worked on this in the past to bridge LISP
> with foreign C code and it's not a straightforward job (it's more
> than just loading a shared library; you have to know how to pass
> arguments to functions, in which registers, in which order, how
> to clean up the stack...). There are probably some libraries out there
> to ease this task (IIRC one was named fficall).
>
> Michael.
>
- Re: Further on MEX, (continued)
- Re: Further on MEX, David Bateman, 2009/01/07
- Re: Further on MEX, John W. Eaton, 2009/01/07
- Re: Further on MEX, David Bateman, 2009/01/07
- Re: Further on MEX, Thomas Weber, 2009/01/08
- Re: Further on MEX, John W. Eaton, 2009/01/27
- Re: Further on MEX, John W. Eaton, 2009/01/07
- Re: Further on MEX, David Bateman, 2009/01/07
- Re: Further on MEX, John W. Eaton, 2009/01/07
- Re: Further on MEX, David Bateman, 2009/01/06
Re: Further on MEX, Michael Goffioul, 2009/01/04
- Re: Further on MEX,
Aravindh Krishnamoorthy <=