From: skaller <skaller@users.sourceforge.net>
To: jtbryant@valdosta.edu
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Marshal and Polymorphism
Date: Fri, 05 Aug 2005 09:17:01 +1000 [thread overview]
Message-ID: <1123197421.6720.56.camel@localhost.localdomain> (raw)
In-Reply-To: <1123187967.3276.94.camel@starlight.valdosta.edu>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
On Thu, 2005-08-04 at 16:39 -0400, Jonathan Bryant wrote:
> My question is: Will this /always/ work (given that the type of data I
> read out of the file is the same)? Is it really that simple?
No, it won't *always* work in the sense that some data
types cannot be serialised. See also 18.9.1 of the manual.
--
John Skaller <skaller at users dot sourceforge dot net>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-08-04 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 18:23 Jonathan Bryant
2005-08-04 20:06 ` [Caml-list] " Stephane Glondu
2005-08-04 20:39 ` Jonathan Bryant
2005-08-04 21:57 ` Stephane Glondu
2005-08-04 23:17 ` skaller [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=1123197421.6720.56.camel@localhost.localdomain \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=jtbryant@valdosta.edu \
/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).