caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Ivan Gotovchits <ivg@ieee.org>
Cc: Alexey Egorov <electreg@list.ru>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Installing library with hidden modules
Date: Tue, 9 May 2017 23:01:12 +0200	[thread overview]
Message-ID: <53B38F9A1D3D4732A24E8EF40B907B3F@erratique.ch> (raw)
In-Reply-To: <CALdWJ+xE+9ciKyU10x-DZ1eZOxG6fbE=HiLgnyXDoHWajdZy8g@mail.gmail.com>

On Monday, 8 May 2017 at 14:49, Ivan Gotovchits wrote:
> An absence of the cmi file, will prevent users from accessing the module directly. The OASIS system provides an easy way to hide modules, with the `InternalModules` field. OASIS will install all the necessary parts of the module (i.e., cmxs, cma, o, a, etc), but will not install the interface part.


If I'm not mistaken you can't do that with module aliases, you'll need the cmi files of the right hand side of the alias (`module M : sig end = M` is invalid syntax). 

Besides it's not because you hide the cmi files that the names won't show up at link time. If your "hidden" toplevel names are generic (let's say `Config`), they will still prevent linking with other libraries that define the same generic names.

Again, you can't hide toplevel names using module aliases.

Best, 

Daniel



  reply	other threads:[~2017-05-09 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-07  5:24 Alexey Egorov
2017-05-08 10:56 ` Daniel Bünzli
2017-05-08 12:49   ` Ivan Gotovchits
2017-05-09 21:01     ` Daniel Bünzli [this message]
2017-05-10 12:17       ` Ivan Gotovchits
2017-05-10 12:43         ` Daniel Bünzli

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=53B38F9A1D3D4732A24E8EF40B907B3F@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    --cc=electreg@list.ru \
    --cc=ivg@ieee.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).