From: Hendrik Tews <H.Tews@cs.ru.nl>
To: caml-list@inria.fr
Subject: Re: [Caml-list] caml_oldify_local_roots takes 50% of the total runtime
Date: Thu, 26 Oct 2006 11:47:10 +0200 [thread overview]
Message-ID: <wwuejsvv275.fsf@tandem.cs.ru.nl> (raw)
In-Reply-To: <f8560b80610251121x10c113faif3e8a50ef0a9415c@mail.gmail.com> (Markus Mottl's message of "Wed, 25 Oct 2006 14:21:14 -0400")
"Markus Mottl" <markus.mottl@gmail.com> writes:
To work around this problem you should store pointers to the C++-objects on
the C++-side, and e.g. associate them with finalized OCaml-values, or
handles which allow you to explicitly deallocate the objects.
I don't quite understand: I only have pointers from C++ to ocaml.
Once constructed the ocaml objects are completely independent
from the C++ ones.
Hendrik
next prev parent reply other threads:[~2006-10-26 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 15:49 Hendrik Tews
2006-10-25 18:21 ` [Caml-list] " Markus Mottl
2006-10-25 19:01 ` skaller
2006-10-26 9:50 ` Hendrik Tews
2006-10-26 13:48 ` Gerd Stolpmann
2006-10-27 11:36 ` Hendrik Tews
2006-10-27 13:17 ` Brian Hurt
2006-10-27 20:05 ` Robert Roessler
2006-10-27 21:16 ` Pierre Etchemaïté
2006-10-30 7:50 ` Hendrik Tews
2006-10-26 9:47 ` Hendrik Tews [this message]
2006-10-26 14:54 ` Markus Mottl
2006-12-15 10:56 ` Hendrik Tews
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=wwuejsvv275.fsf@tandem.cs.ru.nl \
--to=h.tews@cs.ru.nl \
--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;
as well as URLs for NNTP newsgroup(s).