From: Damien Doligez <damien.doligez@inria.fr>
To: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] A nastier example
Date: Mon, 16 May 2005 13:40:32 +0200 [thread overview]
Message-ID: <2d26751672edba48073994fc03b83573@inria.fr> (raw)
In-Reply-To: <200505160115.34416.jon@ffconsultancy.com>
On May 16, 2005, at 02:15, Jon Harrop wrote:
> Very interesting. In summary, is it fair to say that Marshall has
> problems
> with functions when used in the top-level but not with ocamlc- and
> ocamlopt-
> compiled code?
Yes, although it is a very small problem: it would pretty hard for the
average programmer to guarantee that the same function is compiled at
the same address in the top-level that unmarshals the closure.
So the usefulness of marshaling closures from the top-level would be
rather small.
-- Damien
prev parent reply other threads:[~2005-05-16 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 14:51 Julien Verlaguet
2005-05-14 15:09 ` [Caml-list] " Eric Cooper
2005-05-14 15:36 ` Marcin 'Qrczak' Kowalczyk
2005-05-14 15:47 ` Julien Verlaguet
2005-05-15 14:59 ` Vincenzo Ciancia
2005-05-14 19:09 ` [Caml-list] " Jon Harrop
2005-05-15 15:50 ` skaller
2005-05-15 17:24 ` Mark Shinwell
2005-05-16 0:15 ` Jon Harrop
2005-05-16 11:40 ` Damien Doligez [this message]
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=2d26751672edba48073994fc03b83573@inria.fr \
--to=damien.doligez@inria.fr \
--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