From: Matthieu Wipliez <mwipliez@yahoo.fr>
To: caml-list@inria.fr
Subject: Re : [Caml-list] Specifying recursive modules?
Date: Wed, 20 Aug 2008 14:46:23 +0000 (GMT) [thread overview]
Message-ID: <448407.72605.qm@web27005.mail.ukl.yahoo.com> (raw)
Hello,
if you want to use recursive modules in the top-level, it seems that you must use the definition form:
Objective Caml version 3.10.2
# module rec Tmp : sig
type t = Stop | Next of Tmp.t
end =
struct
type t = Stop | Next of Tmp.t
end;;
module rec Tmp : sig type t = Stop | Next of Tmp.t end
#
My guess is that the specification is only valid inside a .mli file. And indeed:
modrec.mli:
module rec Tmp : sig type t = Stop | Next of Tmp.t end
"ocamlc -c modrec.mli" works fine,
while
"ocamlc -c modrec.ml" (with modrec.ml having the same contents as modrec.mli) complains it has a syntax error.
Matthieu
----- Message d'origine ----
> De : Jérémie Lumbroso <jeremie.lumbroso@etu.upmc.fr>
> À : caml-list@inria.fr
> Envoyé le : Mercredi, 20 Août 2008, 16h31mn 51s
> Objet : [Caml-list] Specifying recursive modules?
>
> Hello,
>
> I'd always thought of separating specification and definition as
> simply not possible in OCaml, but OCaml's reference manual (3.10,
> which is, as far as I can tell, the most recent version of the
> documentation) seems to contradict my assumption:
>
> http://caml.inria.fr/pub/docs/manual-ocaml/manual021.html#htoc100
>
> It says that recursive specifications can be written as:
>
>
> module rec : { and ... }
>
>
> What does this mean? When I attempt to use this feature in the
> toplevel, it results in an error:
>
>
> # module rec Tmp : sig
> type t = Stop | Next of Tmp.t
> end**;;**
> Syntax error
>
>
> On the off-chance that OCaml might explicitly need an "and", I also
> tried adding a second dummy module to the definition, but no dice ...
> When I try to use this feature in a .mli/.ml file coupling, I get the
> same (syntax) error. Have I misunderstood the usage? Or has this been
> removed since its introduction (and the documentation not updated
> accordingly)? Or is this a bug?
>
> Jérémie
>
> _______________________________________________
> 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
_____________________________________________________________________________
Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
next reply other threads:[~2008-08-20 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 14:46 Matthieu Wipliez [this message]
2008-08-20 17:15 ` Jérémie Lumbroso
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=448407.72605.qm@web27005.mail.ukl.yahoo.com \
--to=mwipliez@yahoo.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