From: Julien Signoles <Julien.Signoles@lri.fr>
To: ohl@physik.uni-wuerzburg.de
Cc: caml-list@inria.fr
Subject: [Caml-list] Re: Legality of using module types from .mli in .ml
Date: Wed, 15 Jan 2003 17:28:32 +0100 [thread overview]
Message-ID: <3E258C30.9999165E@lri.fr> (raw)
In-Reply-To: <15908.25011.52235.354636@wptx47.physik.uni-wuerzburg.de>
Thorsten Ohl wrote:
>
> I'm often referring to module types defined in an interface file in
> order to reduce redundancy. For example
>
> $ cat a.mli
> module type T = sig val n : int end
> module M : T
>
> $ cat a.ml
> module type T = A.T
> module M : T = struct let n = 42 end
>
> where T can be rather long. Is this legal?
For me, your module type declaration should be illegal in a.ml. But the
ocaml compiler accepts it...
So, is it an ocaml bug ? Orelse what is the exact semantic of (.mli,
.ml) ?
> The reason I'm asking this, is that my shorthand [as in (a.mli, aml)]
> breaks Julien Signoles' defunctorizer.
The previous example doesn't break my defunctorizer :
$ ocamldefun --version
1.02
$ ocamldefun a.mli a.ml
$ cat a.ml
module type T = A.T
module M = struct let n = 42 end
That's ok (normal because a.mli is still in the ocamldefun environment
when a.ml is defunctorized)...
Can you report me your example breaking my defunctorizer ?
Cheers,
Julien Signoles.
--
mailto : Julien.Signoles@lri.fr ; http : www.lri.fr/~signoles
"In theory, practice and theory are the same,
but in practice they are different" (Larry McVoy)
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-01-15 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 19:14 [Caml-list] " Thorsten Ohl
2003-01-15 16:28 ` Julien Signoles [this message]
2003-01-15 16:59 ` [Caml-list] " Thorsten Ohl
2003-01-15 17:37 ` Julien Signoles
2003-01-15 21:57 ` David Brown
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=3E258C30.9999165E@lri.fr \
--to=julien.signoles@lri.fr \
--cc=caml-list@inria.fr \
--cc=ohl@physik.uni-wuerzburg.de \
/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