From: Alex Baretta <alex@baretta.com>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>,
Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Delegation based OO
Date: Tue, 23 Mar 2004 08:27:42 +0100 [thread overview]
Message-ID: <405FE6EE.3080202@baretta.com> (raw)
In-Reply-To: <20040323101402E.garrigue@kurims.kyoto-u.ac.jp>
Jacques Garrigue wrote:
>
> Interesting idea. It would be even more useful now that one can define
> immediate objects (without explicitely defining a class).
> And recent changes on the implementation make direct delegation
> very cheap in terms of code size.
> Note however that one needs to know more clearly which methods are to
> be delegated, so I would rather favor a notation like:
>
> class does_more an_object = object
> delegate does_something to an_object
> ...
> end
Ah! I see your point. Why not? Of course, delegating a class signature
to an object allows you to define explicitely the type components which
the type of does_more imports from the type of an_object. This would
probably help the type checker a lot at giving sensible error messages.
Alex
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-03-23 7:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 10:18 Alex Baretta
2004-03-22 23:01 ` Yamagata Yoriyuki
2004-03-23 0:29 ` Kenneth Knowles
2004-03-23 23:43 ` Yamagata Yoriyuki
2004-03-24 0:45 ` Kenneth Knowles
2004-03-24 10:43 ` Alex Baretta
2004-03-24 14:11 ` Yamagata Yoriyuki
2004-03-24 15:00 ` Alex Baretta
2004-03-24 16:57 ` Kenneth Knowles
2004-03-23 1:14 ` Jacques Garrigue
2004-03-23 7:27 ` Alex Baretta [this message]
2004-03-23 9:01 ` Stefano Zacchiroli
2004-03-23 9:41 ` Alex Baretta
2004-03-23 9:44 ` Jacques Garrigue
2004-03-23 9:47 ` Stefano Zacchiroli
2004-03-23 8:56 ` Correnson Loïc
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=405FE6EE.3080202@baretta.com \
--to=alex@baretta.com \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
/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).