Yes, but that's not a good reason to give up hierarchies completely. The advantage of hierarchies is to have less top-level roots, which reduce the likelihood of clashes with external libraries.
I think that the name clash problem is overblown. Really.
Would it arise concretly I prefer developer cooperation rather than have the problem solved beforehand by forcing a bureaucracy on me (and even the hierarchy cannot prevent the problem completely).
Besides in batteries the maintainers control everything that is below the Batteries module so it is their duty to avoid clashes in their name space and would a clash with an external library B occur I can use Batteries.B to refer to the battery one.
Someone mentionned python's library, if it corresponds to this [1], then I see no hierarchy there (OTOH nobody tells me that python users are actually screaming for a hierarchy on their list).
Best, Daniel [1] http://docs.python.org/library/ _______________________________________________ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
