caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jim Farrand" <jim.farrand@gmail.com>
To: caml-list@yquem.inria.fr
Cc: "Michael Wohlwend" <micha-1@fantasymail.de>
Subject: Re: [Caml-list] The Bridge Pattern in OCaml
Date: Fri, 28 Mar 2008 11:29:18 +0000	[thread overview]
Message-ID: <e16c7bcd0803280429j6c8c7aecl5154b8c227d8020@mail.gmail.com> (raw)
In-Reply-To: <200803281206.30620.micha-1@fantasymail.de>

On 28/03/2008, Michael Wohlwend <micha-1@fantasymail.de> wrote:

> I would make my own format with a version number.
>  Maybe:
>  a complicated binary format,
>  a more text like format like json or yaml or xml *schockhorror*
>  or use a small db for storing, like sqlite.

But how would you encode an O'Caml function/closure as, say, XML?  As
far as I know this isn't possible.

My point is, I want to find some compromise between:
- Representing behaviour as closures (very flexible, but not serializable), and
- Representing behaviour without closures (serializable, but with huge
loss of flexibility wrt. what the behaviour implementations can do -
ie, the framework would have to predict in advance what kind of things
the implementations might want to do in order to provide an encoding
flexible enough).

Regards,
Jim


  reply	other threads:[~2008-03-28 11:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 16:29 Christopher L Conway
2008-03-19 16:51 ` [Caml-list] " Bünzli Daniel
2008-03-19 17:44   ` Christopher L Conway
2008-03-19 18:06     ` Christopher L Conway
2008-03-20  2:07       ` Yaron Minsky
2008-03-20 13:27         ` Martin Jambon
2008-03-20 20:10           ` Christophe Raffalli
2008-03-28 10:44         ` Jim Farrand
2008-03-28 11:06           ` Michael Wohlwend
2008-03-28 11:29             ` Jim Farrand [this message]
2008-03-28 11:57               ` Oliver Bandel
2008-03-28 11:30             ` Oliver Bandel
2008-03-28 11:45               ` Jim Farrand
2008-03-28 11:52                 ` Michael Wohlwend
2008-03-28 12:09                   ` Oliver Bandel
2008-03-28 12:43                     ` Jim Farrand
2008-03-28 18:23                       ` Raoul Duke
2008-03-28 18:29                         ` Robert Fischer
2008-03-28 18:34                         ` David Thomas
2008-03-28 19:14                           ` blue storm
2008-03-28 19:04                         ` Oliver Bandel
2008-03-28 19:05                         ` Mathias Kende
2008-03-28 19:47                         ` Jon Harrop
2008-03-28 23:24                           ` Oliver Bandel
2008-03-31  8:31                         ` Berke Durak
2008-03-29 14:03                       ` Peng Zang
2008-03-28 12:03                 ` Oliver Bandel

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=e16c7bcd0803280429j6c8c7aecl5154b8c227d8020@mail.gmail.com \
    --to=jim.farrand@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=micha-1@fantasymail.de \
    /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).