caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andre Nathan <andre@digirati.com.br>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Mutually recursive types in different modules
Date: Mon, 14 Jul 2008 14:50:16 -0300	[thread overview]
Message-ID: <1216057816.29061.5.camel@andre.mz.digirati.com.br> (raw)
In-Reply-To: <200807141804.32640.jon@ffconsultancy.com>

On Mon, 2008-07-14 at 18:04 +0100, Jon Harrop wrote:
> Yes. See the OCaml Journal article "Tricks with recursion: knots, modules and 
> polymorphism" or Google for the phrase "untying the recursive knot".

Thanks for the pointer. I've found the discussion at

   http://tech.groups.yahoo.com/group/ocaml_beginners/message/9062

where your and Rémi's suggestions were extremely helpful.

Best,
Andre


  reply	other threads:[~2008-07-14 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 16:50 Andre Nathan
2008-07-14 17:04 ` [Caml-list] " Jon Harrop
2008-07-14 17:50   ` Andre Nathan [this message]
2008-07-14 17:57   ` Arthur Chan
2008-07-14 18:04     ` Andre Nathan
2008-07-14 17:43 ` Martin Jambon

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=1216057816.29061.5.camel@andre.mz.digirati.com.br \
    --to=andre@digirati.com.br \
    --cc=caml-list@yquem.inria.fr \
    --cc=jon@ffconsultancy.com \
    /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).