caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Max Skaller <skaller@ozemail.com.au>
To: "Gurr, David (MED, self)" <David.Gurr@med.ge.com>
Cc: Vitaly Lugovsky <vsl@ontil.ihep.su>,
	"Yurii A. Rashkovskii" <yrashk@openeas.org>,
	caml-list@inria.fr
Subject: Re: [Caml-list] Namespace proposal
Date: Mon, 19 Aug 2002 03:05:35 +1000	[thread overview]
Message-ID: <3D5FD3DF.60706@ozemail.com.au> (raw)
In-Reply-To: <D4DBD8568F05D511A1C20002A55C008C09C29529@uswaumsx03medge.med.ge.com>

Gurr, David (MED, self) wrote:

> My two cents worth: Please dont copy package ideas from 
> languages that lack functors.  And Java's package ==
> directory idea is far from beloved by all.  -D

While I agree that 'package == directory' has problems,
languages that do not properly allow installation
of third party packages in such a way as to avoid
name clashes in supporting components, have even
more problems.

Ocaml is in this position. It can't be easily
use in large projects which incorporate many third
party libraries.

Separable installation
is possible but clumbsy (use OCAMLPATH),
but there is no associated mechanism for nameclash avoidance.

In theory, one could use nested modules to avoid nameclashes.
In practice that is out of the question because
it requires all the modules be in one file.

C had exactly the same problem, which is why
C++ added namespaces (independently of
file locations). Python had this problem,
which is why it added packages (dependent on
directory structure).

I personally favour the Eiffel approach because
it is the most flexible -- the dependence of
top level component names on files/directories
is defined by a secondary configuration language.
However, it is a somewhat heavy approach.

One thing is for sure though. The ability to install
third party packages in directories, and the ability
to avoid name clashes in supporting components,
are both required for programming in the large.

Ocaml is so close to a solution: both separable
installation and name clash avoidance are possible,
but the mechanisms cannot be easily integrated.

-- 
John Max Skaller, mailto:skaller@ozemail.com.au
snail:10/1 Toxteth Rd, Glebe, NSW 2037, Australia.
voice:61-2-9660-0850


-------------------
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


  parent reply	other threads:[~2002-08-18 17:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 16:21 Gurr, David (MED, self)
2002-08-15 17:00 ` Vitaly Lugovsky
2002-08-15 21:08   ` [Caml-list] " Michaël Grünewald
2002-08-18 17:05 ` John Max Skaller [this message]
2002-08-30 18:02   ` [Caml-list] Namespace proposal: XML variant Alessandro Baretta
2002-08-30 20:25     ` Jeffrey Palmer
2002-08-30 22:39       ` james woodyatt
2002-08-30 22:51       ` Blair Zajac
  -- strict thread matches above, loose matches on Subject: below --
2002-08-15 20:42 [Caml-list] Namespace proposal Gurr, David (MED, self)
2002-08-16  9:19 ` Vitaly Lugovsky
2002-08-15 20:42 Gurr, David (MED, self)
2002-08-15 17:13 Gurr, David (MED, self)
2002-08-15 17:18 ` Vitaly Lugovsky
2002-08-15 17:53   ` Yurii A. Rashkovskii
2002-08-16  8:52   ` M E Leypold @ labnet
2002-08-16  9:22     ` Vitaly Lugovsky
2002-08-16 10:20       ` Yurii A. Rashkovskii
2002-08-15 17:46 ` Fernando Alegre
2002-08-15  9:43 Ohad Rodeh
2002-08-15 13:27 ` Vitaly Lugovsky
2002-08-15 14:23   ` Yurii A. Rashkovskii
2002-08-15 15:53     ` Vitaly Lugovsky
2002-08-12 20:40 Yurii A. Rashkovskii
2002-08-12 14:19 Yurii A. Rashkovskii
2002-08-12 17:31 ` Michael Vanier

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=3D5FD3DF.60706@ozemail.com.au \
    --to=skaller@ozemail.com.au \
    --cc=David.Gurr@med.ge.com \
    --cc=caml-list@inria.fr \
    --cc=vsl@ontil.ihep.su \
    --cc=yrashk@openeas.org \
    /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).