From: "Tiphaine.Turpin" <Tiphaine.Turpin@free.fr>
To: Keiko Nakata <keiko@kurims.kyoto-u.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OO programming
Date: Mon, 03 Mar 2008 10:40:59 +0100 [thread overview]
Message-ID: <47CBC7AB.9000601@free.fr> (raw)
In-Reply-To: <20080301.005807.125113032.keiko@kurims.kyoto-u.ac.jp>
Keiko Nakata a écrit :
>>> Since there are some people (including me)
>>> who are interested in using functors and recursive modules
>>> in the style of object-oriented context,
>>>
>>>
>> Do you mean including classes in functors, as Jacques Garrigue
>> described, or using modules like classes ?
>>
>
> The former; to include classes in functors.
>
>
>>> I thought that it could be useful to devise
>>> a (camlp4) syntax extension which mitigates this a bit painful verbosity.
>>>
>> camlp4 extensions may help. I already used some for objects (related to
>> initializers), and I plan to investigate it further, possibly borrowing
>> code from Jacques Garrigue. In the context of functors, the problem is
>> that a lot of code would probably remain specific and still need to be
>> written by hand, for example, the row types for classes...
>>
>
> As I see Jacques's code, he gradually extends the module type S
> to S' and S''. Type declarations in module types and type definitions
> in structures involving types event, observer and subject are duplicated
> everywhere with slight modifications.
> Why can we not extend the previously defined module type
> in a less verbose way?
>
I agree. Maybe the idea of using parametric class type definitions (in
WRichT) and defining unparameterized types afterwards (in S'') could be
helpfull, as such definitions can be extended with the "inherit
<class-type>" construct. Otherwise you would need to keep syntaxically
the successive declarations with camlp4 for future use, which is not
very handy. I don't know if there is an equivalent to inherit for
polymorphic variants: "type t' = private [> t | ...] doesn't seem to
work. And using objects to encode variants is possible, but you may be
used to more serious solutions...
Tiphaine Turpin
> We may still need to write row types by hand.
> But I think we should (ideally) do it in a extensible way without duplications.
>
> With best regards,
> Keiko
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2008-03-03 9:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 9:31 Tiphaine Turpin
2008-02-21 9:42 ` [Caml-list] " Erik de Castro Lopo
2008-02-21 13:38 ` Remi Vanicat
2008-02-24 16:33 ` [Caml-list] " Dirk Thierbach
2008-02-25 9:23 ` Tiphaine.Turpin
2008-02-25 15:48 ` Edgar Friendly
2008-02-25 16:02 ` Berke Durak
2008-02-25 20:12 ` Dirk Thierbach
2008-02-25 20:51 ` Tiphaine.Turpin
2008-02-25 23:03 ` Dirk Thierbach
2008-02-25 20:10 ` Dirk Thierbach
2008-02-25 21:49 ` Tiphaine.Turpin
2008-02-25 23:07 ` Dirk Thierbach
2008-02-29 14:22 ` Tiphaine.Turpin
2008-02-26 6:17 ` Jacques Garrigue
2008-02-26 9:36 ` Julien Signoles
2008-02-27 0:25 ` Tiphaine.Turpin
2008-02-27 1:37 ` Jacques Garrigue
2008-02-28 8:34 ` Keiko Nakata
2008-02-28 13:30 ` Andrej Bauer
2008-02-28 15:18 ` Keiko Nakata
2008-02-28 16:02 ` Edgar Friendly
2008-02-29 14:35 ` Tiphaine.Turpin
2008-02-29 15:58 ` Keiko Nakata
2008-03-03 9:40 ` Tiphaine.Turpin [this message]
2008-03-03 10:20 ` Jacques Garrigue
2008-03-03 10:30 ` Tiphaine.Turpin
2008-03-03 15:18 ` Keiko Nakata
2008-03-03 19:25 ` Tiphaine Turpin
2008-03-04 14:00 ` Keiko Nakata
2008-02-27 7:40 ` Dirk Thierbach
2008-02-27 14:04 ` Tiphaine.Turpin
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=47CBC7AB.9000601@free.fr \
--to=tiphaine.turpin@free.fr \
--cc=caml-list@inria.fr \
--cc=keiko@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).