From: Alessandro Baretta <alex@baretta.com>
To: Chris Hecker <checker@d6.com>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] camlimages vs. labltk
Date: Fri, 28 Mar 2003 06:33:56 +0100 [thread overview]
Message-ID: <3E83DEC4.8030307@baretta.com> (raw)
In-Reply-To: <4.3.2.7.2.20030327113554.0369d060@localhost>
Chris Hecker wrote:
>
>> Do you see what the problems are with the module system?
>
>
> Okay, let me restate your point ... Right?
>
Yes. I'm glad I made my point clear.
>
> Assuming we're on the same page about all of the above, do you think the
> syntax of the module system should or should not be overloaded for
> namespaces?
It doesn't really matter to me. I don't advocate the
explicit use of the "namespace" keyword. I don't care at
all, so long as naming problems are kept at the naming level
and linking problems at the linking level.
> 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
I think this solution is unduly complex to implement, but
then again, I am a caml rider, not a caml breeder...
> 2. define a new namespace system and syntax (or reuse the module
> syntax, not sure what the issues are there)
This is my suggestion: use a minor backward compatible
syntax extension to allow for namespace use.
> Are there any other options? Did I get all of that right?
Not that I know of.
> I agree that if the module semantics make it so that pack must link all
> submodules and run all initialization then it's too heavyweight and it
> either needs to be changed or there needs to be a new system.
Right.
Cheers, Chris.
Alex
-------------------
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 5:28 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 [this message]
2003-03-28 5:35 ` David Brown
2003-03-28 14:10 ` Damien Doligez
2003-03-28 15:00 ` Sven Luther
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=3E83DEC4.8030307@baretta.com \
--to=alex@baretta.com \
--cc=caml-list@inria.fr \
--cc=checker@d6.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