From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gares@fettunta.org>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by sympa.inria.fr (Postfix) with ESMTPS id 2781F7F6CC
	for <caml-list@sympa.inria.fr>; Thu,  5 Feb 2015 13:27:45 +0100 (CET)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  enrico.tassi@inria.fr) identity=pra; client-ip=94.23.69.127;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="gares@fettunta.org";
  x-sender="enrico.tassi@inria.fr";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  gares@fettunta.org) identity=mailfrom;
  client-ip=94.23.69.127;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="gares@fettunta.org";
  x-sender="gares@fettunta.org"; x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@fettunta.org) identity=helo;
  client-ip=94.23.69.127;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="gares@fettunta.org";
  x-sender="postmaster@fettunta.org";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C7AgDWYNNUdH9FF15ahCbJbkMBAQEBAREBDB1ChA0BBTpPCxgJJQ8FKIhhBNYpkBWDAIETBZg9AZJqgWcBC4IegzABAQE
X-IPAS-Result: A0C7AgDWYNNUdH9FF15ahCbJbkMBAQEBAREBDB1ChA0BBTpPCxgJJQ8FKIhhBNYpkBWDAIETBZg9AZJqgWcBC4IegzABAQE
X-IronPort-AV: E=Sophos;i="5.09,523,1418079600"; 
   d="scan'208";a="98974256"
Received: from fettunta.org ([94.23.69.127])
  by mail3-smtp-sop.national.inria.fr with ESMTP; 05 Feb 2015 13:27:44 +0100
Received: from birba.invalid (birba.inria.fr [138.96.192.36])
	by fettunta.org (Postfix) with ESMTPSA id 1A6EFD45A
	for <caml-list@inria.fr>; Thu,  5 Feb 2015 13:27:44 +0100 (CET)
Received: from gares by birba.invalid with local (Exim 4.84)
	(envelope-from <gares@birba.invalid>)
	id 1YJLX5-0007bT-TG
	for caml-list@inria.fr; Thu, 05 Feb 2015 13:27:43 +0100
Date: Thu, 5 Feb 2015 13:27:43 +0100
From: Enrico Tassi <enrico.tassi@inria.fr>
To: caml-list@inria.fr
Message-ID: <20150205122743.GA28748@birba.invalid>
References: <20150202103256.GA30053@birba.invalid>
 <54D33020.6010707@lexifi.com>
 <54D33EC3.2050809@inria.fr>
 <54D34AF2.1010001@lexifi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54D34AF2.1010001@lexifi.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: [Caml-list] unmarshaling large data from string on 32 bits

On Thu, Feb 05, 2015 at 11:50:26AM +0100, Alain Frisch wrote:
> I hope you know precisely which values go into the closures or not (exception
> slots, global mutable data structures, etc)...

This is exactly why we _don't_ marshal closures in Coq.  As far as I
know "what goes into a closure" is not documented, so I removed all
closures from the state we send on the wire.

I don't know why PMP ended up thinking we do, but I've just checked, no
Marshal.Closure flag ;-)

Thanks for the heads up anyway,
-- 
Enrico Tassi