From: skaller <skaller@users.sourceforge.net>
To: briand@aracnet.com
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] mutually recursive classes (yes - again)
Date: 10 Jan 2005 18:35:32 +1100 [thread overview]
Message-ID: <1105342532.3534.17.camel@pelican.wigram> (raw)
In-Reply-To: <16865.64337.367003.181340@soggy.deldotd.com>
On Mon, 2005-01-10 at 14:49, briand@aracnet.com wrote:
> let z1 = new a1 ?? ?? ;;
> let z2 = new a2 ?? ?? ;;
>
> Obviously I need to "ground" the recursion somehow,
Try
let rec
z1 = new a1 z1 z2 and
z2 = new a2 z2 z1
;;
> I have about 7 more classes in this recursion-fest and a nice orderly
> way to handle it would be VERY helpful.
Try
class a1 (x:a1 option) (y:a2 option) =
a1 option has value
Some of a1 | None
and so is like a C pointer.
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
prev parent reply other threads:[~2005-01-10 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 3:49 briand
2005-01-10 7:35 ` skaller [this message]
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=1105342532.3534.17.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=briand@aracnet.com \
--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).