From: Martin Jambon <martin.jambon@ens-lyon.org>
To: Yaron Minsky <yminsky@gmail.com>
Cc: Christopher L Conway <cconway@cs.nyu.edu>,
Caml Mailing List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] The Bridge Pattern in OCaml
Date: Thu, 20 Mar 2008 14:27:13 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0803201414001.9125@martin.ec.wink.com> (raw)
In-Reply-To: <891bd3390803191907q5838ee66u83cb35e549805af0@mail.gmail.com>
On Wed, 19 Mar 2008, Yaron Minsky wrote:
> On Wed, Mar 19, 2008 at 2:06 PM, Christopher L Conway <cconway@cs.nyu.edu>
> wrote:
>
>>
>> Are people here using this language feature in the real world? If so, how?
>
>
> For what it's worth, not at Jane Street. We've looked at using existential
> types once or twice, but have yet to find a really compelling application.
> We don't really use objects much either.
>
> I'm actually a bit puzzled by your original post, in that I don't have a
> clear sense of what kind of situations you've run up against where using
> poor-man's objects (e.g., collections of closures wrapped up in a bundle)
> doesn't do the job. On the whole, I've found that collections of closures
> are easier to think about than objects precisely because you don't have to
> worry about subtyping. I'd be quite curious to hear about concrete examples
> where that approach doesn't fit well.
I find the biggest advantage of objects over records to be the same as
polymorphic variants over classic variants:
- reusability of method names or variant names
- the same interface can be defined independently by 2 libraries without
creating a dependency between them; later, objects (resp. poly.
variants) coming from one library or another can be used
interchangeably.
Martin
--
http://wink.com/profile/mjambon
http://martin.jambon.free.fr
next prev parent reply other threads:[~2008-03-20 13:28 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 [this message]
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
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=Pine.LNX.4.64.0803201414001.9125@martin.ec.wink.com \
--to=martin.jambon@ens-lyon.org \
--cc=caml-list@yquem.inria.fr \
--cc=cconway@cs.nyu.edu \
--cc=yminsky@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