Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Chet Murthy <murthy.chet@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] C++ for Ocaml FFI bindings
Date: Mon, 02 Jan 2017 21:54:17 -0800	[thread overview]
Message-ID: <7033084.csZPQNGq1J@twitter> (raw)

Hi, I've been watching the discussions over the years regarding FFI
bindings from Ocaml.  I've built a ton of such bindings using Camlidl.
I've used some done using Ctypes.  And it's always hard.  But
recently, I've come to the conclusion that bindings against C++ would
be (shockingly, yes I know) -easier- than against C.

To demonstrate this, and because I had need of it, I've writte a
little IDL compiler, along with an example FFI wrappering of the C++
Rocksdb API.  Only as an example.  The code is raw, and really
.... raw.  But it works, works well, and is dreamily easy to add new
entry-points to.  I'm hoping that over the next few weeks, as I use
this, I'll add tests, more examples, and documentation.

  --> oboy, does it need documentation (if anybody but me is -ever-
      gonna use it)

Right now though, I just thought I'd send this note, to try to raise
the subject that ....

  Maybe C++ is a ripe target for FFIs from Ocaml?

I've released the code (such as it is) on Github:

https://github.com/chetmurthy/ocaml-cppffigen

https://github.com/chetmurthy/ocaml-rocksdb

Please don't take this as an advertisement for the code.  But do take
it as an advertisement for the -idea-.

Cheers,
--chet--


             reply	other threads:[~2017-01-03  5:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03  5:54 Chet Murthy [this message]
2017-01-03 10:34 ` Fabrice Le Fessant
2017-01-03 12:59   ` immanuel litzroth

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=7033084.csZPQNGq1J@twitter \
    --to=murthy.chet@gmail.com \
    --cc=caml-list@inria.fr \
    /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