From: "Milan Stanojević" <milanst@gmail.com>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: Markus Mottl <markus.mottl@gmail.com>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] strange error with packed modules and module type of
Date: Fri, 8 Jun 2012 16:36:12 -0400 [thread overview]
Message-ID: <CAKR7PS9anGZ2yxTXpKwqk6rgfF_xq+rjEJ9AbASrNZptSYWd0w@mail.gmail.com> (raw)
In-Reply-To: <5ECBEDB2-9C7C-45B7-98F7-36E10B2BB07D@math.nagoya-u.ac.jp>
>> Should I just file this problem on ocaml mantis?
>
> This is the right behavior.
> To understand it, you should distinguish between the interface (or abstract signature)
> and the concrete type of a module (its strengthened signature).
I was actually referring to my original problem.
Can you point out what I was doing wrong there?
prev parent reply other threads:[~2012-06-08 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 0:25 Milan Stanojević
2012-05-30 2:30 ` Markus Mottl
2012-06-07 19:53 ` Milan Stanojević
2012-06-07 23:37 ` Jacques Garrigue
2012-06-08 20:36 ` Milan Stanojević [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=CAKR7PS9anGZ2yxTXpKwqk6rgfF_xq+rjEJ9AbASrNZptSYWd0w@mail.gmail.com \
--to=milanst@gmail.com \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
--cc=markus.mottl@gmail.com \
/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