On Tue, Nov 18, 2008 at 12:34:28PM +0100, Daniel Bünzli wrote: >> For example I prefer using the least amount of opening of modules, to >> make it easier to see where the values come from > Same here. This is why I'm a little bit sceptical about this hierarchy.
Well, the problem of not knowing where a value comes from is more a tool problem, than an argument against hierarchies. The compiler knows where a value comes from, it is only hard to get this information back. IIRC one of this year OSP addressed precisely that problem. > Besides Hierarchies are anyway limited in their descriptive power > and one day you'll find something that will fit in two places, Rope > is already an example being both Data.Persistent and Data.Text. 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. Even though in some cases you might need to choose among two different places, it is rarely the case in practice. Also remember that the Batteries hierarchy was not meant to allocate *all* existing libraries into a common hierarchy, that interpretation came from Rich's comment. So the real question is, according to what you currently see in the hierarchy, do you like it or not? Do you something placed in weird places? Cheers. -- Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7 [EMAIL PROTECTED],pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/ Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime _______________________________________________ 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
