From: Dave Benjamin <dave@ramenlabs.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Easier FFI
Date: Thu, 20 Dec 2007 20:37:09 -0700 [thread overview]
Message-ID: <476B34E5.2060108@ramenlabs.com> (raw)
In-Reply-To: <200712201639.15513.jon@ffconsultancy.com>
Jon Harrop wrote:
> For example, why can't we have a generic FFI library that allows us to use any
> external library (unsafely) without leaving OCaml? Then we could write or
> generate our bindings entirely in OCaml and forget about these C stubs.
I would love something like this. I've used "ctypes", a similar library
for Python, a few times, and it has really come in handy. Not something
I want to use often (at least not directly), but for those times when
use of an unsupported C library is necessary, it's so nice to have the
ability to stay within the language rather than writing a bunch of
wrapper code. I wonder if something like ctypes would translate well to
a statically typed language like OCaml.
http://starship.python.net/crew/theller/ctypes/
next prev parent reply other threads:[~2007-12-21 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 16:39 Jon Harrop
2007-12-21 3:37 ` Dave Benjamin [this message]
2007-12-21 3:54 ` [Caml-list] " Jon Harrop
2007-12-21 11:20 ` Richard Jones
2008-02-01 17:13 ` Alan Falloon
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=476B34E5.2060108@ramenlabs.com \
--to=dave@ramenlabs.com \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.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