From: Alain Frisch <alain@frisch.fr>
To: Dumitru Potop-Butucaru <dumitru.potop_butucaru@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Bug in the module system of version 3.12.0+beta1
Date: Thu, 22 Jul 2010 04:29:19 +0200 [thread overview]
Message-ID: <4C47ACFF.9020409@frisch.fr> (raw)
In-Reply-To: <4C473F45.6020307@inria.fr>
On 7/21/2010 8:41 PM, Dumitru Potop-Butucaru wrote:
> If I understand well, what I try to do is impossible for
> some deep theoretical reason. Can someone explain this
> to me, or point me to a relevant paper explaining it?
Turning a module type into a module is not possible in general: if the
module type defines runtime components like values, what module would
you produce?
Then there is a sub-category of module types that can be turned into
module in a natural way (module type with only type, class types, module
types, exceptions, and recursive or non-recursive modules with the same
constraints on their components). By pure coincidence, I played a few
months ago with the idea of adding a construction to the language that
would turn such a module type into a module expression (I had no
concrete motivation to do that). This is available in the
module_of_module_type branch of the OCaml svn repository.
Alain
next prev parent reply other threads:[~2010-07-22 2:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 13:38 Dumitru Potop-Butucaru
2010-07-21 14:13 ` [Caml-list] " Jeremy Yallop
2010-07-21 15:49 ` rossberg
2010-07-21 18:41 ` Dumitru Potop-Butucaru
2010-07-22 2:29 ` Alain Frisch [this message]
2010-07-22 6:36 ` Dumitru Potop-Butucaru
2010-07-22 6:18 ` Jacques Garrigue
[not found] ` <4C47E768.4080507@inria.fr>
[not found] ` <9454F06C-C286-4A1F-8A9F-CA3B27F8E3BB@gmail.com>
2010-07-22 7:07 ` Dumitru Potop-Butucaru
2010-07-22 9:37 ` rossberg
2010-07-22 10:44 ` Jacques Garrigue
2010-07-22 12:28 ` Dumitru Potop-Butucaru
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=4C47ACFF.9020409@frisch.fr \
--to=alain@frisch.fr \
--cc=caml-list@inria.fr \
--cc=dumitru.potop_butucaru@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;
as well as URLs for NNTP newsgroup(s).