From: Bardur Arantsson <spam@scientician.net>
To: caml-list@inria.fr
Subject: Re: memory handling with native code
Date: Thu, 24 Aug 2006 18:47:55 +0200 [thread overview]
Message-ID: <eckl7s$5qt$1@sea.gmane.org> (raw)
In-Reply-To: <20060824085934.198440@gmx.net>
Michael Wohlwend wrote:
> I'm trying to make an interface to a c++ lib of a friend of me, it's getting better, but questions about
> the memory management came up:
> Should I wrap the pointer in a custom object?
[-- snip mumble about unbroken lines ;) --]
Since we're on this subject: I was wondering whether anyone on the list
has investigated if it's possible to use the C++ boost::shared_ptr<> or
tr1::shared_ptr<> for that matter and OCaml's custom blocks to
interoperate so that one can avoid having to do manual custom
block/pointer management on the C/C++ side of things?
I've always found the manual custom block/pointer management to be one
of the more annoying aspects of OCaml's FFI.
Cheers,
--
Bardur Arantsson
<bardurREMOVE@THISscientician.net>
- I didn't have a blunt object with me, so I said "OK".
David Letterman, 'The Late Show'
prev parent reply other threads:[~2006-08-24 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 8:59 Michael Wohlwend
2006-08-24 15:46 ` [Caml-list] " skaller
2006-08-24 16:47 ` Bardur Arantsson [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='eckl7s$5qt$1@sea.gmane.org' \
--to=spam@scientician.net \
--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