Matt Gushee wrote:
>>High on my wish-list for the core ocaml system is
>>namespaces or something similiar to help resolve this problem.
> 
> Agreed. Even in my fairly short time programming OCaml, I've had to
> struggle several times to find a good name for a module.

What I'd like is to be able to create a unique name for a project, and 
then use it as a namespace containing non-unique module names.  For 
example, I use the domain saucecode.org for my Caml work.  I'd like to 
be able to create a Saucecode namespace, and within it create module 
names representing libraries, without worrying about whether those names 
are unique in the whole Caml community.  So a user could use my 
Saucecode.Foo module, and someone else's Extlib.Foo module, without any 
conflict.

Today I can create a Saucecode module with a Foo module inside it, but I 
can only define Saucecode once.  That means that I would have to package 
all my libraries as a single download, and anyone who wanted to use one 
library would have to use them all.

Be

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