From: "David MENTRE" <david.mentre@gmail.com>
To: "Artem Prysyazhnuk" <temofey@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Marshaling between different ocaml version
Date: Thu, 27 Apr 2006 09:04:11 +0200 [thread overview]
Message-ID: <3d13dcfc0604270004h7a5b8216sc5b39bff0db3ae6f@mail.gmail.com> (raw)
In-Reply-To: <e7b5cc180604262338y52d0f2e6ra57531d9cd50fc86@mail.gmail.com>
Hello,
2006/4/27, Artem Prysyazhnuk <temofey@gmail.com>:
> step by step. I active use marshaling for interop between remote
> client/server parts of system. So if server will be compiled on 3.07+2
> and client will be compiled on 3.09.2 is this combination ok for
> marshaling between client/server?
It should work. Marshalling code has not changed since 1996:
http://caml.inria.fr/pub/ml-archives/caml-list/2005/12/8c8ed24a48841b1f9879b60fa9a756d2.fr.html
I have not reviewed release notes of latest OCaml versions but as far
as I remember, nothing has changed on that side.
Best wishes,
d.
prev parent reply other threads:[~2006-04-27 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 6:38 Artem Prysyazhnuk
2006-04-27 7:04 ` David MENTRE [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=3d13dcfc0604270004h7a5b8216sc5b39bff0db3ae6f@mail.gmail.com \
--to=david.mentre@gmail.com \
--cc=caml-list@inria.fr \
--cc=temofey@gmail.com \
/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).