From: ketti <kattlachan@gmail.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: "caml-list caml-list" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] mutually recursive modules
Date: Sat, 22 Mar 2008 22:20:56 +0100 [thread overview]
Message-ID: <6ebe51ce0803221420h272bec70ne92695651f6b2b38@mail.gmail.com> (raw)
In-Reply-To: <7B22B0CF-8E65-434A-9EF7-0C20EBE618E8@erratique.ch>
> > is it possible to put mutually recursive modules in different files?
>
> No.
Yes.
If you wrap them in functors.
next prev parent reply other threads:[~2008-03-22 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 19:22 Jacques Le Normand
2008-03-22 19:37 ` [Caml-list] " Daniel Bünzli
2008-03-22 21:20 ` ketti [this message]
2008-03-23 16:59 ` Jacques Le Normand
2008-03-23 18:37 ` ketti
2008-03-24 9:21 ` rossberg
-- strict thread matches above, loose matches on Subject: below --
2006-01-17 8:55 Brendan Miller
2006-01-17 10:21 ` [Caml-list] " Jacques Garrigue
2006-01-17 12:13 ` skaller
2005-12-02 10:15 Jonathan Roewen
2005-12-06 17:33 ` Alain Frisch
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=6ebe51ce0803221420h272bec70ne92695651f6b2b38@mail.gmail.com \
--to=kattlachan@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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).