From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Damien Doligez <Damien.Doligez@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] camlimages vs. labltk
Date: Fri, 28 Mar 2003 16:00:28 +0100 [thread overview]
Message-ID: <20030328150028.GA9211@iliana> (raw)
In-Reply-To: <F8D1C46A-6126-11D7-B6B4-0003930FCE12@inria.fr>
On Fri, Mar 28, 2003 at 03:10:04PM +0100, Damien Doligez wrote:
> On Thursday, March 27, 2003, at 08:46 PM, Chris Hecker wrote:
>
> >It seems like there are a couple different options:
> >
> >1. relax the semantics of module inclusion/initialization so that
> >-pack can simultaneously provide the nested module syntax of
> >Package.Foo but it doesn't have to link all of the submodules, like a
> >cma
> >
> >2. define a new namespace system and syntax (or reuse the module
> >syntax, not sure what the issues are there)
> >
> >Are there any other options? Did I get all of that right?
>
> How about a solution based on renaming ? Let's say I have two modules
> from different programmers, both named "Mylib", and I want to use them
> in my program. I cannot because the module system does not allow two
> different modules with the same name to coexist. The obvious solution
> is a tool that renames one of the Mylib modules. Then I can use both
> modules in one program.
>
> It becomes a little more complex when you consider that a module also
> imports other modules, referenced by their names. For example, I can
> have (in addition to the two "Mylib" modules) another pair of modules,
> Extlib and Superlib, written by two other programmers, and I want to
> use them both in my program. And Extlib uses one of the Mylib, Superlib
> uses the other one. Now if I rename the second Mylib into Mylib2,
> I also have to tell Superlib to use Mylib2 instead of Mylib.
>
> So I need a tool to rename modules, both as exports and as imports,
> then I can use any module I want, without changing anything in the
> language, and without the need for a universal naming scheme.
Does this not sound as a ugly hack ?
Would it not be easier to have something akin to -pack, but without its
technical problems, and have each library pack its module into a
namespace propper to this library ?
If all library did this by default, at library build time, then there
would be no need to rename the imports, since those imports would
already have the modified (that is Library.Module) names ?
Friendly,
Sven Luther
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-03-28 15:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 19:33 Shivkumar Chandrasekaran
2003-03-26 8:25 ` Alessandro Baretta
2003-03-26 8:33 ` Sven Luther
2003-03-26 9:00 ` Alessandro Baretta
2003-03-26 10:50 ` Sven Luther
2003-03-26 11:24 ` Alessandro Baretta
2003-03-26 11:38 ` Sven Luther
2003-03-26 19:08 ` Chris Hecker
2003-03-26 21:08 ` Alessandro Baretta
2003-03-27 17:23 ` David Brown
2003-03-27 19:46 ` Chris Hecker
2003-03-28 5:33 ` Alessandro Baretta
2003-03-28 5:35 ` David Brown
2003-03-28 14:10 ` Damien Doligez
2003-03-28 15:00 ` Sven Luther [this message]
2003-03-30 10:06 ` Damien Doligez
2003-03-30 10:38 ` Sven Luther
2003-04-01 14:14 ` [Caml-list] naming conflicts (was: camlimages vs. labltk) Damien Doligez
2003-04-01 15:05 ` Benjamin C. Pierce
2003-04-01 19:51 ` Chris Hecker
2003-04-08 10:33 ` Damien Doligez
2003-03-31 1:21 ` [Caml-list] camlimages vs. labltk Chris Hecker
2003-03-30 9:26 ` Alessandro Baretta
2003-03-26 18:49 ` Shivkumar Chandrasekaran
2003-03-26 10:48 ` Stefano Zacchiroli
2003-03-26 10:55 ` Sven Luther
2003-03-26 14:10 ` Stefano Zacchiroli
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=20030328150028.GA9211@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=Damien.Doligez@inria.fr \
--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