From: skaller <skaller@ozemail.com.au>
To: Damien <Damien.Pous@ens-lyon.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Mutually recursive classes
Date: 07 Nov 2003 18:34:38 +1100 [thread overview]
Message-ID: <1068190478.6194.51.camel@pelican> (raw)
In-Reply-To: <20031103114816.50edea0c.Damien.Pous@ens-lyon.fr>
On Mon, 2003-11-03 at 21:48, Damien wrote:
> Hello,
>
> I would like to create two mutually recursive classes,
There is a mechanical workaround for this.
You first parameterise your classes,
then you use a type/class definition
instantiating the parameters: the latter
construction allows recursive 'and's.
For example,
class type A' ['B'] ..
class type B' ['A'] ..
type A = B A' and B = A B'
[and similarly for classes, using let instead]
-------------------
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-11-07 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 10:48 Damien
2003-11-03 13:53 ` Didier Remy
2003-11-07 7:34 ` skaller [this message]
2003-11-03 17:41 pous damien
2003-11-04 17:52 ` Damien
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=1068190478.6194.51.camel@pelican \
--to=skaller@ozemail.com.au \
--cc=Damien.Pous@ens-lyon.fr \
--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;
as well as URLs for NNTP newsgroup(s).