From: Evgeny Roubinchtein <zhenya1007@gmail.com>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] One more question about Gc.finalise
Date: Sun, 18 Jun 2017 19:45:25 -0400 [thread overview]
Message-ID: <CAGYXaSamWJCQyYqqa934mpEk=zf+TDGd5WXKPHQGhio54GyayA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
Dear OCaml users and developers,
I have one more question about Gc.finalise to which I couldn't find an
answer in the documentation.
Suppose I do, "Gc.finalise f v", and the function f makes the value v
reachable again. If I want f to be called again should v become
unreachable again, do I need to again call "Gc.finalise f v", after f has
"revived" v?
My experimentation _seems_ to suggest that I do, but there is always the
danger that I am misinterpreting the results of my experiment. :-)
Thank you in advance!
--
Best,
Zhenya
[-- Attachment #2: Type: text/html, Size: 701 bytes --]
next reply other threads:[~2017-06-18 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 23:45 Evgeny Roubinchtein [this message]
2017-06-19 6:02 ` François Bobot
2017-06-19 12:04 ` Jacques-Henri Jourdan
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='CAGYXaSamWJCQyYqqa934mpEk=zf+TDGd5WXKPHQGhio54GyayA@mail.gmail.com' \
--to=zhenya1007@gmail.com \
--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).