From: Alessandro Baretta <alex@baretta.com>
To: Sven Luther <luther@dpt-info.u-strasbg.fr>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] camlimages vs. labltk
Date: Wed, 26 Mar 2003 12:24:56 +0100 [thread overview]
Message-ID: <3E818E08.2000505@baretta.com> (raw)
In-Reply-To: <20030326105006.GA3891@iliana>
Sven Luther wrote:
> On Wed, Mar 26, 2003 at 10:00:03AM +0100, Alessandro Baretta wrote:
>
>>
>>Sven Luther wrote:
>>Sven, someone on this list wisely pointed out that you buy
>>nothing by telling someone else "You don't need that
>>feature". We do need namespaces. It might not be paramount:
> As for side-effects, i didn't really think about that, but i guess that
> you could easily implement the modules so that the side effect do happen
> when you call a module initialization function or something such. I
> don't think it really is good practice to use toplevel global side
> effect for library code anyway.
We now have a new language feature: it's called
You Don't Need It (TM), patent pending ;)
>>So -pack is good, but
>>namespaces are still a necessary feature to Ocaml as to any
>>industrial level programming language.
>
>
> No, the namespace feature is already there, altough not much used in
> reality, the problems are elsewhere.
Modules are a very powerful theoretical instrument with a
profound algebraic meaning, rooted in category theory. This
is all very good, and I appreciate it. But namespaces are
something _ELSE_. And they too are a good thing to have. Why
don't we just stop this "You don't need it thing" about any
language feature we don't already have. Ocaml is a cool
language. It's my primary language for developing business
applications. I earn a living with it. I know what I need
and what I don't need. Namespaces are a useful tool, aside
from the algebraically based module system: they simply
provied a means for mangling module names so as to avoid
name clashes.
There are many different ways of implementing a namespace
system. We need to think of an implementation orthogonal to
the module system, so as to add functionality without
introducing conflicts with the module system. I would
appreciate a lot more a -namespace option to ocamlmklib than
a -pack option to ocamlc. This feature would have to go with
such additional language constructs such as an "in" operator
for namespace resolution. Such language constructs have
already been implemented as camlp4 syntax extensions and are
already available out there.
> Friendly,
>
> Sven Luther
>
Cheers,
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-26 11:19 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 [this message]
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
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=3E818E08.2000505@baretta.com \
--to=alex@baretta.com \
--cc=caml-list@inria.fr \
--cc=luther@dpt-info.u-strasbg.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