caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Timothy Bourke <tim@tbrk.org>
To: "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
Cc: Jun Inoue <jun.lambda@gmail.com>, caml list <caml-list@inria.fr>
Subject: Re: [Caml-list] Type That's Concrete From Within A Library Abstract From Without
Date: Fri, 6 Jul 2018 10:05:19 +0200	[thread overview]
Message-ID: <20180706080519.3xfypjvfxsvj5kyk@xocuter> (raw)
In-Reply-To: <CADK7aFOLQDAkPkK8SAp59J24Puj1E=uh-bTeH645OxgQLgWzRg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

* Nicolás Ojeda Bär [2018-04-26 17:03 +0200]:
>This is a limitation of module packs. However, there is a much better
>alternative to module packs in the form of module aliases which will
>allow you to do what you want.

Thank you for this suggestion. We have tried it on a development 
branch of the Sundials/ML library and it works quite well.

>4. compile the individual files in the library with
>
>  ocamlc -no-alias-deps -open Sundials -c sundials__private.ml
>  ocamlc -no-alias-deps -open Sundials -c sundials__public.ml

For the record, two details are worth noting regarding the "-open 
Sundials".

1. It works well with Merlin if one adds the line

      FLG -open Sundials

   to the .merlin file.

2. It does not work well with ocamldoc, which has no -open option.
   Maybe there is another way around this problem?

In any case, there currently seem to be some other limitations around 
ocamldoc and module aliases.

Tim.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2018-07-06  8:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 14:18 Jun Inoue
2018-04-26 14:27 ` Malcolm Matalka
2018-04-26 15:03 ` Nicolás Ojeda Bär
2018-04-26 15:14   ` Nicolás Ojeda Bär
2018-07-06  8:05   ` Timothy Bourke [this message]
2018-07-06  8:52     ` Gabriel Scherer
2018-07-06  9:03       ` Timothy Bourke
2018-04-26 15:06 ` Ivan Gotovchits
2018-04-27  5:48   ` Jun Inoue
2018-04-27  6:05     ` Jacques Garrigue
2018-04-27  8:53       ` Jun Inoue
2018-04-27 10:40         ` Mikhail Mandrykin
2018-04-27 11:21         ` Elie Canonici Merle

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=20180706080519.3xfypjvfxsvj5kyk@xocuter \
    --to=tim@tbrk.org \
    --cc=caml-list@inria.fr \
    --cc=jun.lambda@gmail.com \
    --cc=nicolas.ojeda.bar@lexifi.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;
as well as URLs for NNTP newsgroup(s).