From: Enrico Tassi <enrico.tassi@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] unmarshaling large data from string on 32 bits
Date: Thu, 5 Feb 2015 11:33:56 +0100 [thread overview]
Message-ID: <20150205103356.GA9849@birba.invalid> (raw)
In-Reply-To: <54D33EC3.2050809@inria.fr>
On Thu, Feb 05, 2015 at 10:58:27AM +0100, Pierre-Marie Pédrot wrote:
> Both workarounds would not work. Indeed, we use closure marshalling in
> Coq, which is not supported by the two proposed implementations.
JFTR no, we don't mashal closures.
Still a custom unmarshaler is a bit pulp for me...
Best,
--
Enrico Tassi
next prev parent reply other threads:[~2015-02-05 10:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 10:32 Enrico Tassi
2015-02-02 12:00 ` Gabriel Scherer
2015-02-02 13:08 ` Pierre-Marie Pédrot
2015-02-04 16:47 ` Enrico Tassi
2015-02-04 23:51 ` Gerd Stolpmann
2015-02-05 8:56 ` Alain Frisch
2015-02-05 9:01 ` Gabriel Scherer
2015-02-05 9:34 ` Alain Frisch
2015-02-05 9:58 ` Pierre-Marie Pédrot
2015-02-05 10:33 ` Enrico Tassi [this message]
2015-02-05 10:50 ` Alain Frisch
2015-02-05 12:22 ` Fabrice Le Fessant
2015-02-05 12:24 ` Alain Frisch
2015-02-05 12:27 ` Enrico Tassi
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=20150205103356.GA9849@birba.invalid \
--to=enrico.tassi@inria.fr \
--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).