From: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
To: orbitz@ezabel.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Scoped Bound Resource Management just for C++?
Date: Thu, 10 Feb 2011 11:59:52 +0100 [thread overview]
Message-ID: <20110210105952.GX17055@localhost> (raw)
In-Reply-To: <20110210103953.GU17055@localhost>
Le Thursday 10 Feb 2011 à 11:39:53 (+0100), Guillaume Yziquel a écrit :
> Le Wednesday 09 Feb 2011 à 10:15:43 (-0500), orbitz@ezabel.com a écrit :
And even with all that has been mentioned, there isn't really a way to
avoid the fact that closures may still hold on to your value.
> Otherwise you would need to refine the type system of OCaml to include
> information as to whether an argument can be attached to another
> datastructure inside a given function. I do not see why it could not be
> done, but I do not see why it should be done.
That's perhaps the only way to avoid closures from holding to your
value, by forbidding partial evaluation, and enforcing full evaluation.
But that's way overkill.
--
Guillaume Yziquel
next prev parent reply other threads:[~2011-02-10 11:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 23:57 orbitz
2011-02-09 0:46 ` Guillaume Yziquel
2011-02-09 0:48 ` Jacques Garrigue
2011-02-09 6:25 ` dmitry grebeniuk
2011-02-09 12:01 ` rossberg
2011-02-09 15:15 ` orbitz
2011-02-09 16:14 ` Gerd Stolpmann
2011-02-09 16:52 ` David Rajchenbach-Teller
2011-02-09 17:54 ` orbitz
2011-02-09 21:50 ` Jon Harrop
2011-02-10 8:10 ` David Rajchenbach-Teller
2011-02-10 10:39 ` Guillaume Yziquel
2011-02-10 10:59 ` Guillaume Yziquel [this message]
2011-02-09 19:11 ` Florian Weimer
2011-02-09 20:10 ` Andreas Rossberg
2011-02-09 20:45 ` Florian Weimer
2011-02-09 21:12 ` Andreas Rossberg
2011-02-10 21:31 ` Florian Weimer
2011-02-09 18:03 ` Jon Harrop
2011-02-09 20:47 ` Norman Hardy
2011-02-09 21:00 ` Gabriel Scherer
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=20110210105952.GX17055@localhost \
--to=guillaume.yziquel@citycable.ch \
--cc=caml-list@inria.fr \
--cc=orbitz@ezabel.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;
as well as URLs for NNTP newsgroup(s).