From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Big array with data managed by another value
Date: Fri, 14 Nov 2008 16:10:13 +0100 [thread overview]
Message-ID: <15DBBCF2-79EF-4F08-A589-3E1B9B4EECB5@erratique.ch> (raw)
In-Reply-To: <4A8FA99F-D6C3-4D99-AC8D-E17CEE94C88F@erratique.ch>
Le 14 nov. 08 à 15:42, Daniel Bünzli a écrit :
> I'm not sure I understand what you want to do (what is the original
> value ?).
I think I understood now, the original value was the custom block.
If you were using the custom block only for finalization issues (not
serialization, hashing etc.) then one solution would be to replace
your custom block type by the bigarray itself. An register the
bigarray with Gc.finalise to deallocate the C pointer at the
appropriate time. Then you have
type t = bigarray
let to_bigarray x = x
and no problems.
Best,
Daniel
next prev parent reply other threads:[~2008-11-14 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 14:03 Romain Beauxis
2008-11-14 14:42 ` [Caml-list] " Daniel Bünzli
2008-11-14 15:10 ` Daniel Bünzli [this message]
2008-11-14 15:58 ` Romain Beauxis
2008-11-14 16:23 ` Daniel Bünzli
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=15DBBCF2-79EF-4F08-A589-3E1B9B4EECB5@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--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).