From: Mark Shinwell <mshinwell@janestreet.com>
To: Tom Ridge <tom.j.ridge+list@googlemail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Best practices for avoiding global module name clashes?
Date: Fri, 19 May 2017 11:16:54 +0100 [thread overview]
Message-ID: <CAM3Ki76hUEchx3qxr8Q5OpGQvrgE+C7WXdx0e6L0zqk7MPWTqQ@mail.gmail.com> (raw)
In-Reply-To: <CABooLwMU+pH1fJTsB_sMoQY4BBHy-_we==K34PH6xi35LyXshA@mail.gmail.com>
Well, this is one option for building libraries without packs and
without clashes (not to mention building things fast):
https://github.com/janestreet/jbuilder
(See the manual under the "library" stanza, for example. Module
aliases and various renamings are used to avoid packs.)
Mark
On 19 May 2017 at 11:01, Tom Ridge <tom.j.ridge+list@googlemail.com> wrote:
> Many projects include modules named "Prelude" "Monad" etc etc.
>
> What is the current best practice to avoid clashes? Prefix with some short
> string related to the library name? I don't really want to use packing.
>
> Thanks
prev parent reply other threads:[~2017-05-19 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 10:01 Tom Ridge
2017-05-19 10:16 ` Mark Shinwell [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=CAM3Ki76hUEchx3qxr8Q5OpGQvrgE+C7WXdx0e6L0zqk7MPWTqQ@mail.gmail.com \
--to=mshinwell@janestreet.com \
--cc=caml-list@inria.fr \
--cc=tom.j.ridge+list@googlemail.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).