From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rich@annexia.org>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83])
	by sympa.inria.fr (Postfix) with ESMTPS id 4F7F17EE25
	for <caml-list@sympa.inria.fr>; Wed,  6 Nov 2013 15:20:50 +0100 (CET)
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  rich@annexia.org) identity=pra; client-ip=80.68.91.176;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="rich@annexia.org";
  x-sender="rich@annexia.org"; x-conformance=sidf_compatible
Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of
  rich@annexia.org designates 80.68.91.176 as permitted sender)
  identity=mailfrom; client-ip=80.68.91.176;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="rich@annexia.org";
  x-sender="rich@annexia.org"; x-conformance=sidf_compatible;
  x-record-type="v=spf1"
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@furbychan.cocan.org) identity=helo;
  client-ip=80.68.91.176;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="rich@annexia.org";
  x-sender="postmaster@furbychan.cocan.org";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkgFAKJPelJQRFuw/2dsb2JhbABagweDPBO8eoEkFnSCJQEBBTo/EAsYCRMSDwUoIYgYAb8OhhWJRAeDIIEQA5gLkguDJjw
X-IPAS-Result: AkgFAKJPelJQRFuw/2dsb2JhbABagweDPBO8eoEkFnSCJQEBBTo/EAsYCRMSDwUoIYgYAb8OhhWJRAeDIIEQA5gLkguDJjw
X-IronPort-AV: E=Sophos;i="4.93,647,1378850400"; 
   d="scan'208";a="41262451"
Received: from furbychan.cocan.org ([80.68.91.176])
  by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 06 Nov 2013 15:20:13 +0100
Received: from rich by furbychan.cocan.org with local (Exim 4.80)
	(envelope-from <rich@annexia.org>)
	id 1Ve3yS-0002uh-Fn; Wed, 06 Nov 2013 14:20:48 +0000
Date: Wed, 6 Nov 2013 14:20:48 +0000
From: "Richard W.M. Jones" <rich@annexia.org>
To: Jean Krivine <jean.krivine@gmail.com>
Cc: Lukasz Stafiniak <lukstafi@gmail.com>, caml users <caml-list@inria.fr>
Message-ID: <20131106142048.GC10737@annexia.org>
References: <CAEQoNCmmht1CvRUQnops2zT9ufX4XQ=rgyXwdSSbY6Y_-fDUXg@mail.gmail.com>
 <CAJMfKEW7aWPm1M+xCQ60PmSZxD6Mb8e+AuhnZmik7PuHYgUkQg@mail.gmail.com>
 <CAJMfKEXWeUjOxk2tJ9i0E9-w=rCt5cxm1eGARWsMqC3Le0hdmw@mail.gmail.com>
 <CAEQoNCk6wYD5BEMFaq0NCtYsgCVp+Jxbepk=0xwRSBcBh=yyFQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAEQoNCk6wYD5BEMFaq0NCtYsgCVp+Jxbepk=0xwRSBcBh=yyFQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [Caml-list] out-of-the-heap 'a arrays ?

On Wed, Nov 06, 2013 at 10:19:42AM +0100, Jean Krivine wrote:
> It seems that Ancient requires the values that are moved to be immutable
> full point. I understand that there is a problem if you have pointers from
> Ancient Heap to Ocaml Heap. But what about pointers that are internal to
> the Ancient Heap ? Am I talking nonsense? Sorry if I do.

You can definitely create pointers between ancient objects.  You
just have to be really careful about what you're doing.

It's not too hard to understand -- I would suggest reading
the implementation.

Rich.

-- 
Richard Jones
Red Hat