From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] RE: understanding weak
Date: Sat, 1 Nov 2008 01:08:17 +0000 [thread overview]
Message-ID: <200811010108.17426.jon@ffconsultancy.com> (raw)
In-Reply-To: <5EFD4D7AC6265F4D9D3A849CEA9219191AB114@LAXA.intra.cea.fr>
On Thursday 30 October 2008 18:48:26 CUOQ Pascal wrote:
> Warren Harris <warren@metaweb.com> wrote:
> > I'd like to understand better how ocaml's weak pointers operate.
>
> You will be interested in the following important article:
> http://portal.acm.org/citation.cfm?id=1411308
Is this freely available anywhere?
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next prev parent reply other threads:[~2008-11-01 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081030182019.EEBC5BBB7@yquem.inria.fr>
2008-10-30 18:48 ` CUOQ Pascal
2008-10-30 19:12 ` [Caml-list] " Daniel Bünzli
2008-10-30 19:35 ` Warren Harris
2008-10-30 23:06 ` Alain Frisch
2008-10-31 8:33 ` Rémi Vanicat
2008-11-01 1:08 ` Jon Harrop [this message]
2008-11-01 10:37 ` [Caml-list] " Stefano Zacchiroli
2008-11-01 15:18 ` kirillkh
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=200811010108.17426.jon@ffconsultancy.com \
--to=jonathandeanharrop@googlemail.com \
--cc=caml-list@yquem.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).