From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: Damien.Pous@ens-lyon.fr
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] polymorphic methods
Date: Thu, 13 Mar 2003 18:27:02 +0900 [thread overview]
Message-ID: <20030313182702L.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <20030313100402.02e1ce82.Damien.Pous@ens-lyon.fr>
From: Damien <Damien.Pous@ens-lyon.fr>
> > > Does someone know why the following class type
> > > is not accepted ?
> > >
> > > # class type a = object method m: 'a. (#a as 'a) -> unit end;;
> > > The abbreviation #a expands to type #a but is used with type < .. >
> > [...]
> > Now, the serious part: can such a type be defined?
> > After working a bit on this riddle, I'm afraid the answer is no.
> > The reason is that there is no way to recurse on a quantified
> > polymorphic method rather than on the whole object.
> > The closest I found is:
> > class type a =
> > object method m : < d : 'b. (< m : 'a; .. > as 'b) -> unit > as 'a
> > end
> > The dummy wrapper <d : 'b. ... > is just there to allow one to recurse
> > on the polymoprhic method itself. You can call the method m by doing
> > [a#m#d a'] in place of [a#m a'].
> I worked with this class type, but it is a bit tedious :-(
>
> My goal is to define a tree, whose node's type is a class
> type a_t, containing a method for adding children.
> but the child type can be any subtype of a_t
>
> * this method can safely be typed [a_t->unit], but this will require a
> lot of coercions in the rest of the code...
>
> * that's why I wanted to type it ['a. (#a_t as 'a)->unit] (i.e. the
> coercion is written only once, in the method)
>
> using your trick, I obtained the attached code. It works fine,
> but that's not really a beautiful piece of code !
And I would not have expected it to be!
This was just a theoretical answer.
If you are bothered by coercions, you may have a look at the trick in
lablgtk, which avoids polymorphic methods: give the parent as
argument.
let new_node ?parent () =
let n = new node in
begin match parent with None -> ()
| Some (p : #a_t) -> p#add (n :> a_t)
end;
n
You can also do the trick in an initializer.
Alternatively, you might just have an interface of a_t without
the method m. This way you have no problem with recursion:
class type a0_t = object
... everything but add ...
end
class type a_t = object
inherit a0_t
method add : #a0_t -> unit
end
> I don't know what do you mean when saying
> "such a type cannot be defined", in fact, I could define this
> equivalent (I think it is...) :
>
> >#class type a_t = object
> > method m: 'a.(<m: 'a -> unit; ..> as 'a) -> unit
> >end
This is not equivalent: the m in a_t is a polymorphic method, but not
the one in the recursion. Polymorphic and monomorphic methods are
incompatible, so you cannot pass an a_t to m.
Jacques Garrigue
-------------------
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:[~2003-03-13 9:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 23:07 Damien
2003-03-13 0:56 ` brogoff
2003-03-13 1:56 ` Jacques Garrigue
2003-03-13 9:04 ` Damien
2003-03-13 9:27 ` Jacques Garrigue [this message]
2003-03-13 14:49 ` Damien
2003-03-13 9:41 ` Olivier Andrieu
-- strict thread matches above, loose matches on Subject: below --
2015-12-18 9:18 Christoph Höger
2015-12-18 10:07 ` Leo White
2002-08-23 15:46 [Caml-list] Polymorphic methods Frederic Tronel
2002-08-23 17:32 ` Fred Smith
2002-08-23 18:21 ` Remi VANICAT
2002-07-14 23:16 [Caml-list] polymorphic methods nadji
2002-07-15 1:05 ` Jacques Garrigue
2002-07-15 2:08 ` Brian Smith
2002-07-15 16:24 ` nadji
2001-11-19 15:29 [Caml-list] Polymorphic methods Alain Frisch
2001-11-20 0:29 ` Jacques Garrigue
2001-11-20 9:33 ` Alain Frisch
2001-11-20 20:55 ` Xavier Leroy
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=20030313182702L.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--cc=Damien.Pous@ens-lyon.fr \
--cc=caml-list@pauillac.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