From: "Milan Stanojević" <milanst@gmail.com>
To: Ashish Agarwal <agarwal1975@gmail.com>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] module Cset clash
Date: Thu, 11 Dec 2014 13:42:23 -0500 [thread overview]
Message-ID: <CAKR7PS_2kxFfWekMc7xGV4VYVXAJze5HbQ9QRrZ8s4o9W7Hyzg@mail.gmail.com> (raw)
In-Reply-To: <CAMu2m2JrNMi7L_vjLSaSWpcBERR4eNq+9Lh8FYKFv4ndX=cDDA@mail.gmail.com>
In 4.02 you can add prefixes to the modules, in effect creating
namespaces, but it requires work in build systems. I'm not sure any
build system is making use of this right now.
On Thu, Dec 11, 2014 at 1:21 PM, Ashish Agarwal <agarwal1975@gmail.com> wrote:
> A Cset module is provided by both the pa_ulex and re packages, leading to:
>
> The files /Users/ashish/.opam/4.02.1/lib/ulex/pa_ulex.cma
> and /Users/ashish/.opam/4.02.1/lib/re/re.cma
> disagree over interface Cset
>
> Is the only solution for one of the packages to change the name?
>
prev parent reply other threads:[~2014-12-11 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 18:21 Ashish Agarwal
2014-12-11 18:42 ` 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=CAKR7PS_2kxFfWekMc7xGV4VYVXAJze5HbQ9QRrZ8s4o9W7Hyzg@mail.gmail.com \
--to=milanst@gmail.com \
--cc=agarwal1975@gmail.com \
--cc=caml-list@inria.fr \
/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