From: "Ashish Agarwal" <agarwal1975@gmail.com>
To: "Christian Sternagel" <christian.sternagel@uibk.ac.at>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Default module type?
Date: Thu, 25 Sep 2008 09:02:07 -0400 [thread overview]
Message-ID: <d8be5ae20809250602s6928b68ax800bce32fa7d26da@mail.gmail.com> (raw)
In-Reply-To: <48DB81D8.1080101@uibk.ac.at>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
That is correct. You have to define a module type within an ml file, and
then include that. See the following thread on the beginner's list.
http://tech.groups.yahoo.com/group/ocaml_beginners/message/8992
However, I never did find out why. Why does the compiler not create a module
type MySig from an mli file mySig.mli? This would be very convenient.
On Thu, Sep 25, 2008 at 8:19 AM, Christian Sternagel <
christian.sternagel@uibk.ac.at> wrote:
> Hi there,
>
> when I have a file m.ml I can use
>
> include M
>
> in other *.ml files to include the content of m.ml. However, the same
> functionality for module types seems not to exist. I have an interface file
> m.mli and want to use
>
> include M
>
> within another *.mli file (so that I only have to write the documentation
> for module M once, namely in m.mli). But there is no
> module type M. Does anyone have the same problem and/or have a solution?
>
> cheers
>
> christian sternagel
>
> _______________________________________________
> 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
>
[-- Attachment #2: Type: text/html, Size: 2088 bytes --]
prev parent reply other threads:[~2008-09-25 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 12:19 Christian Sternagel
2008-09-25 13:02 ` Ashish Agarwal [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=d8be5ae20809250602s6928b68ax800bce32fa7d26da@mail.gmail.com \
--to=agarwal1975@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=christian.sternagel@uibk.ac.at \
/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).