From: "Jim Farrand" <jim.farrand@gmail.com>
To: "Oliver Bandel" <oliver@first.in-berlin.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] The Bridge Pattern in OCaml
Date: Fri, 28 Mar 2008 12:43:42 +0000 [thread overview]
Message-ID: <e16c7bcd0803280543p259a8c49y54ebf73fafe6417e@mail.gmail.com> (raw)
In-Reply-To: <1206706146.47ecdfe275806@webmail.in-berlin.de>
On 28/03/2008, Oliver Bandel <oliver@first.in-berlin.de> wrote:
> Zitat von Michael Wohlwend <micha-1@fantasymail.de>:
> Creating a datastrzucture, while creatzing the functionality.
> And later, when you want to serialize what you have build up,
> write that datastructure, you build by your own, to a file.
> and when rereading it, this means: re-create the functionality from the
> datastructure.
>
> Isn't this, what is looked for, here?
Yes, this definitely solves the problem and meets the requirements I specified.
In Haskell, it would be very neat - define a Monad for composing the
ASTs and then code just like you would any other Haskell program,
you're just using a different Monad from normal.
In O'Caml, a lot less neat because the user providing the behaviour
suddenly isn't really coding the algorithm in O'Caml, but creating a
data-structure that represents the computation.
But still, it definitely gets the job done.
> This is in a way langauge implementation.
> Isn't it?
Yes, indeed. I guess that's what makes me hesitate. When a fairly
simple problem like "allow calling modules to provide custom behaviour
with serialisation" is answered with "implement a sub-language", it
makes me worry that either the language or my design is inappropriate
for the job, especially when other languages solve the same problem
with relative ease.
So I guess, I'm hoping for something more. :) (I'm very demanding I
know, but this list regularly puts forward answer of such pure genius
that I figure it's worth asking[1])
Thanks for your thoughts on the issue,
Jim
[1] http://ocaml.janestcapital.com/?q=node/18
next prev parent reply other threads:[~2008-03-28 12:43 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 [this message]
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=e16c7bcd0803280543p259a8c49y54ebf73fafe6417e@mail.gmail.com \
--to=jim.farrand@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=oliver@first.in-berlin.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