* [Caml-list] Best practices for avoiding global module name clashes?
@ 2017-05-19 10:01 Tom Ridge
2017-05-19 10:16 ` Mark Shinwell
0 siblings, 1 reply; 2+ messages in thread
From: Tom Ridge @ 2017-05-19 10:01 UTC (permalink / raw)
To: caml-list
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 313 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Caml-list] Best practices for avoiding global module name clashes?
2017-05-19 10:01 [Caml-list] Best practices for avoiding global module name clashes? Tom Ridge
@ 2017-05-19 10:16 ` Mark Shinwell
0 siblings, 0 replies; 2+ messages in thread
From: Mark Shinwell @ 2017-05-19 10:16 UTC (permalink / raw)
To: Tom Ridge; +Cc: caml-list
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-05-19 10:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-19 10:01 [Caml-list] Best practices for avoiding global module name clashes? Tom Ridge
2017-05-19 10:16 ` Mark Shinwell
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).