From: William Chesters <williamc@paneris.org>
To: caml-list@inria.fr
Subject: RE: first class, recursive, mixin modules (was: RE: first class m odules)
Date: Fri, 9 Feb 2001 22:45:36 +0100 (CET) [thread overview]
Message-ID: <14980.25762.184960.213741@beertje.william.bogus> (raw)
In-Reply-To: <112C6E8A1B25D34BB27D48D2FD2E96CFC942C0@TVP-MSG-02.europe.corp.microsoft.com>
Claudio Russo writes:
> I'm not really sure it bites that many, but I'd like to be told
> otherwise. It does really hit you when trying to
> implement Chris Okasakis elegant bootstrapped data structures, or
> emulate object oriented things with modules. (Together with first-class
> and recursive structure, you can model quite a bit of object oriented
> stuff, but I'm not sure how natural or efficient this appproach is.)
I've always been interested by this; you get an intriguing cross
between (in C++ terms) templates and classes.
next prev parent reply other threads:[~2001-02-10 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 9:41 Claudio Russo
2001-02-09 16:47 ` Brian Rogoff
2001-02-09 21:45 ` William Chesters [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-15 14:13 Dave Berry
2001-01-14 20:51 Brian Rogoff
2001-01-12 12:12 Claudio Russo
2001-01-11 18:15 Dave Berry
2001-01-11 20:01 ` Brian Rogoff
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=14980.25762.184960.213741@beertje.william.bogus \
--to=williamc@paneris.org \
--cc=caml-list@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