From: "Daniel Bünzli" <daniel.buenzli@epfl.ch>
To: Tom Hawkins <tom@confluent.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Nesting Modules
Date: Wed, 2 Nov 2005 13:09:55 +0100 [thread overview]
Message-ID: <B7D5978F-7328-496B-B364-EF398E2A873D@epfl.ch> (raw)
In-Reply-To: <4368AA69.4090504@confluent.org>
Le 2 nov. 05 à 13:00, Tom Hawkins a écrit :
> Building a cma/cmxa is fine -- I am working on a library after
> all. But for this to work, how are the mli files handled? I tried
> several variations of the following, but again, I'm faced with
> "Unbound module type Bottom":
It is true that when I applied the scheme I described to my own code
I inelegantly cut and pasted Bottom's type in Top's one.
It seems that although a compiled file a.ml defines a module named A,
a compiled file a.mli doesn't define a module type A, strange
asymmetry. Apparently an old feature wish about this is in the
bugtracking system [1]. Maybe we should wish again ? The problem of
the wish is that granting it could break existing code.
Daniel
[1] <http://pauillac.inria.fr/bin/caml-bugs/feature%20wish?id=1471>
next prev parent reply other threads:[~2005-11-02 12:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 16:59 Tom Hawkins
2005-11-02 1:39 ` [Caml-list] " Pietro Abate
2005-11-02 6:43 ` Martin Jambon
2005-11-02 1:45 ` Robert Roessler
2005-11-02 2:03 ` Chris King
2005-11-02 8:42 ` Daniel Bünzli
2005-11-02 12:00 ` Tom Hawkins
2005-11-02 12:09 ` Daniel Bünzli [this message]
[not found] ` <Pine.LNX.4.62.0511011028340.4466@ganymede.cs.unm.edu>
2005-11-02 4:47 ` Tom Hawkins
2005-11-02 9:46 ` Richard Jones
2005-11-02 9:57 ` Daniel Bünzli
2005-11-02 10:47 ` Richard Jones
2005-11-02 10:57 ` Daniel Bünzli
2005-11-02 11:27 ` Richard Jones
2005-11-02 11:59 ` Tom Hawkins
2005-11-02 12:33 ` Richard Jones
2005-11-02 13:11 ` Christophe TROESTLER
2005-11-02 14:02 ` Tom Hawkins
2005-11-02 14:36 ` Gerd Stolpmann
2005-11-02 13:34 ` Oliver Bandel
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=B7D5978F-7328-496B-B364-EF398E2A873D@epfl.ch \
--to=daniel.buenzli@epfl.ch \
--cc=caml-list@yquem.inria.fr \
--cc=tom@confluent.org \
/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).