From: Joel Reymont <joelr1@gmail.com>
To: "Mathias Kende" <mathias@kende.fr>
Cc: <caml-list@inria.fr>
Subject: Re: RE : [Caml-list] Examples of creating C++ library bindings
Date: Mon, 19 Feb 2007 14:35:38 +0000 [thread overview]
Message-ID: <525CC2C9-90A4-4FF8-95B1-70EBE0F68D41@gmail.com> (raw)
In-Reply-To: <000101c75431$e7948730$c09ec781@mathiasens>
On Feb 19, 2007, at 2:26 PM, Mathias Kende wrote:
> http://caml.inria.fr/pub/docs/manual-ocaml/manual032.html#htoc232
>
> Is it what you're looking for ?
Mathias, thanks for the pointer. I'm looking for a reasonably small
but idiomatic (is there such a thing with FFI?) example of C++
bindings. I would like to know if I should I prefer classes or use
modules, for example. Do I go with SWIG or do it manually?
Thanks, Joel
--
http://wagerlabs.com/
next prev parent reply other threads:[~2007-02-19 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 14:08 Joel Reymont
2007-02-19 14:26 ` RE : [Caml-list] " Mathias Kende
2007-02-19 14:35 ` Joel Reymont [this message]
2007-02-19 18:32 ` Nathaniel Gray
2007-02-19 18:46 ` micha
2007-02-19 19:43 ` Nathaniel Gray
2007-02-19 14:43 ` micha
2007-02-19 23:02 ` Robert Roessler
2007-02-20 12:55 ` Dário Abdulrehman
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=525CC2C9-90A4-4FF8-95B1-70EBE0F68D41@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@inria.fr \
--cc=mathias@kende.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;
as well as URLs for NNTP newsgroup(s).