From: "Ashish Agarwal" <agarwal1975@gmail.com>
To: "Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] About namespaces
Date: Sat, 22 Nov 2008 14:30:59 -0500 [thread overview]
Message-ID: <d8be5ae20811221130m7e814c17pe566377144591a1a@mail.gmail.com> (raw)
In-Reply-To: <1227216556.7676.31.camel@Blefuscu>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
> Among other things, this means that if I write an extension MyList to
> List and someone else writes and extension HisList to List, there is no
> automated way to merge these, I need to write yet another module
> LatestList to be able to use both extensions at the same time.
Merging these with the import command you propose requires an external
configuration. Would that be any easier than using include to define a new
module? Or is there supposed to be some other benefit I'm missing?
[-- Attachment #2: Type: text/html, Size: 710 bytes --]
prev parent reply other threads:[~2008-11-22 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 21:29 David Rajchenbach-Teller
2008-11-20 21:57 ` [Caml-list] " Christophe Raffalli
2008-11-21 9:24 ` David Rajchenbach-Teller
2008-11-22 19:30 ` Ashish Agarwal [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=d8be5ae20811221130m7e814c17pe566377144591a1a@mail.gmail.com \
--to=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;
as well as URLs for NNTP newsgroup(s).