Re: Languages with well-integrated Foreign Function Interface to learn from?

anton@mips.complang.tuwien.ac.at (Anton Ertl)
Tue, 21 Jul 2009 11:29:48 GMT

          From comp.compilers

Related articles
Languages with well-integrated Foreign Function Interface to learn fro lerno@dragonascendant.com (=?ISO-8859-1?Q?Christoffer_Lern=F6?=) (2009-07-21)
Re: Languages with well-integrated Foreign Function Interface to learn anton@mips.complang.tuwien.ac.at (2009-07-21)
Re: Languages with well-integrated Foreign Function Interface to learn barry.j.kelly@gmail.com (Barry Kelly) (2009-07-21)
Re: Languages with well-integrated Foreign Function Interface to learn haberg_20080406@math.su.se (Hans Aberg) (2009-07-21)
Re: Languages with well-integrated Foreign Function Interface to learn jgd@cix.compulink.co.uk (2009-07-21)
Re: Languages with well-integrated Foreign Function Interface to learn uninverted@lavabit.com (Nathan Seese) (2009-07-22)
Re: Languages with well-integrated Foreign Function Interface to learn gene.ressler@gmail.com (Gene) (2009-07-22)
Re: Languages with well-integrated Foreign Function Interface to learn dot@dotat.at (Tony Finch) (2009-07-26)
[11 later articles]
| List of all articles for this month |

From: anton@mips.complang.tuwien.ac.at (Anton Ertl)
Newsgroups: comp.compilers
Date: Tue, 21 Jul 2009 11:29:48 GMT
Organization: Institut fuer Computersprachen, Technische Universitaet Wien
References: 09-07-074
Keywords: code, design, bibliography

=?ISO-8859-1?Q?Christoffer_Lern=F6?= <lerno@dragonascendant.com> writes:
>I'd like to research FFI in various languages, basically to find the
>best FFI-solution and copy from that one.
>It's likely that I will restrict myself to interfacing with C, so if
>there are elegant solutions integrating with C, and more clunky but
>flexible that are more general, I probably prefer the ones that
>exclusively target C.
>
>What I'm looking for is syntax, to what extent automatic conversion of
>arguments are done, how to handle callbacks, memory management, how to
>create structured data (i.e. structs in the case of C) etc.


You may find the following paper interesting:


@InProceedings{ertl07euroforth,
    author = "M. Anton Ertl",
    title = "Gforth's libcc {C} Function Call Interface",
    booktitle = "23rd EuroForth Conference",
    year = "2007",
    editor = "M. Anton Ertl",
    pages = "7--11",
    URL = "http://www.complang.tuwien.ac.at/papers/ertl07euroforth.ps.gz",
    pdfurl = "http://www.complang.tuwien.ac.at/anton/euroforth2007/papers/ertl.pdf",
    OPTnote = "not refereed",
    abstract = "A major problem in our earlier proposal for a C
interface was that a part of the interface was not
portable between platforms. The libcc interface solves
this problem by using a C compiler and its
\code{.h}-files. The \code{.h}-files contain knowledge
about the specific platform, and the C compiler
automatically inserts the necessary conversions between
Forth and C types. In this paper we describe the libcc
implementation and interface. We also discuss how a
Forth-C interface might be standardized.",
}


Another thing you will want to look at is SWIG <www.swig.org>.


>[[...] all the FFI seems rather ad-hoc and language specific. -John]


There are lots of language-specific problems (e.g., the type systems
of the two languages involved, or the interaction of the garbage
collector with the C functions), so I think that it's necessary to be
language-specific, although SWIG tries to at least factor out the
language-independent parts.


- anton
--
M. Anton Ertl
anton@mips.complang.tuwien.ac.at
http://www.complang.tuwien.ac.at/anton/



Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.