From: David Fox <dsfox@cogsci.ucsd.edu>
To: Dave Berry <dave@kal.com>
Cc: jeanmarc.eber@lexifi.com, David Fox <dsfox@cogsci.ucsd.edu>,
caml-list@inria.fr
Subject: Re: [Caml-list] Foreign function interface generator with example s
Date: 23 Apr 2001 19:44:26 -0700 [thread overview]
Message-ID: <lu7l0b10fp.fsf@hci.ucsd.edu> (raw)
In-Reply-To: Dave Berry's message of "Mon, 23 Apr 2001 11:32:42 +0100"
I was not aware of CamlIDL, or even of IDL itself until just now. The
major difference I can see from a quick look at the docs is that the
IDL system converts ML data structures into C data structures and back
again for every function invocation. Mine simply allocates a string
of the appropriate size for each structure and leaves it in there.
Dave Berry <dave@kal.com> writes:
> Curiousity impels me to ask: How does David's system compare with CamlIDL?
> Is there a need for an FFI interface at a lower-level than CamlIDL? I'm
> interested because I've worked on FFIs for ML in the past, and we gradually
> moved more and more towards IDL-based solutions. So I'd be interested to
> hear what limitations people see with this approach (or with the particular
> CamlIDL implementation, as I hope to use that some day).
>
> Dave.
>
>
> -----Original Message-----
> From: jeanmarc.eber@lexifi.com [mailto:jeanmarc.eber@lexifi.com]
> Sent: Friday, April 20, 2001 10:37
>
> I think that an *easy* FFI (you call it "out of the box") is one of the
> most important stuff to do for Ocaml. Most of us know that there aren't
> any *impossibilities* (more or less anything *can* be done, but you have
> to use exactly the correct macros etc...), but its not .... yes, say
> "out of the box".
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
prev parent reply other threads:[~2001-04-24 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 10:32 Dave Berry
2001-04-24 2:44 ` David Fox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lu7l0b10fp.fsf@hci.ucsd.edu \
--to=dsfox@cogsci.ucsd.edu \
--cc=caml-list@inria.fr \
--cc=dave@kal.com \
--cc=jeanmarc.eber@lexifi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox