From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] The Bridge Pattern in OCaml
Date: Fri, 28 Mar 2008 13:03:30 +0100 [thread overview]
Message-ID: <1206705810.47ecde9222d8e@webmail.in-berlin.de> (raw)
In-Reply-To: <e16c7bcd0803280445g525c9788v3c75511d23be9943@mail.gmail.com>
Zitat von Jim Farrand <jim.farrand@gmail.com>:
> On 28/03/2008, Oliver Bandel <oliver@first.in-berlin.de> wrote:
> > It seems that you already know, what things you
> > want to write to the files
>
> No.
>
> The opposite in fact. I want to be able to serialize things I (the
> framework designer) never even thought of. I want the users of my
> framework to have maximum flexibility to implement whatever behaviour
> they like, without restricted them to the things I thought of putting
> into the file format.
[...]
OK, so I misunderstood your needs.
sorry, I didn't read the thread completely and just jumped in.
>
> O'Caml marshalling is in the right direction (take any closure and
> serialize it, this is very flexible in this respect), but it is far
> to
> restricted in other ways to be of use (file format tied to particular
> executable).
OK. Marhsal-module is nice, but there are disadvantages:
if the marshalled data is loaded but was corrupted, this
can crash your program!
So I would never recommend to use it.
It also possibly could be a security hole, when using that module.
Another reason why I would never recommend it's usage.
Beter write your own implementation of the serialization
on top of OCaml, without of Marhsalling-module (which
is too deep inside the internals of Ocaml, and therefore make things
possibly unreliable!).
Ciao,
Oliver
prev parent reply other threads:[~2008-03-28 12:03 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
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 [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=1206705810.47ecde9222d8e@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--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