From: "Dr. Thomas Fischbacher" <t.fischbacher@soton.ac.uk>
To: Markus Mottl <markus.mottl@gmail.com>
Cc: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Custom blocks and finalization
Date: Thu, 30 Apr 2009 19:17:20 +0100 [thread overview]
Message-ID: <49F9EB30.5090302@soton.ac.uk> (raw)
In-Reply-To: <f8560b80904300846v734fdd58lb6040e7b1b456a1@mail.gmail.com>
Markus Mottl wrote:
> Otherwise, it might be helpful if the OCaml-team could consider
> whether this situation can be improved. For example not being allowed
> to register/unregister roots to values seems overly restrictive, since
> global roots (e.g. for protecting OCaml-callback closures) sometimes
> need to be associated with C-values (e.g. for allowing some external
> C-library to efficiently perform callbacks into OCaml).
I would just like to point out that the OCaml/Python based "nmag"
(/"nsim") MPI-parallel micromagnetic simulator does this a lot, and
it is actually needed for a seamless vice-versa integration of
Python/Caml closures (i.e. one can freely call Python closures
from within OCaml, and OCaml closures from within Python.)
I think we could change this in such a way that registering the
finalizer is done by a detour through OCaml wherever the
problem arises, but it just feels very wrong to do so, somehow...
--
best regards,
Thomas Fischbacher
t.fischbacher@soton.ac.uk
next prev parent reply other threads:[~2009-04-30 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 15:46 Markus Mottl
2009-04-30 18:17 ` Dr. Thomas Fischbacher [this message]
[not found] ` <49FB04A9.3090008@soton.ac.uk>
2009-05-01 16:00 ` [Caml-list] " Markus Mottl
2009-05-06 16:30 ` Dr. Thomas Fischbacher
2009-05-06 16:54 ` Markus Mottl
2009-05-06 17:53 ` Dr. Thomas Fischbacher
2009-05-08 9:36 ` Xavier Leroy
2009-05-08 13:48 ` Markus Mottl
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=49F9EB30.5090302@soton.ac.uk \
--to=t.fischbacher@soton.ac.uk \
--cc=caml-list@yquem.inria.fr \
--cc=markus.mottl@gmail.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