On Thu, Apr 16, 2009 at 2:16 AM, Konrad Hinsen <konrad.hin...@laposte.net>wrote:
[...] > > I think it would be useful to formalize this concept of a "standard > library" that is a single entity from the point of view of users who > just want to download a jar file and get going. A standard library > would also define certain conventions and APIs and thus prevent > future users from having to choose among ten essentially equivalent > but yet incompatible libraries for file handling or for XML parsing. > > Of course there are a couple of open questions: Who decides what goes > into the standard library? Who maintains it in the long run? Are > external dependencies allowed and if yes, how are they handled? If contrib is to be viewed as a standard library for Clojure then I think it makes perfect sense to allow external dependencies. I don't know of any language with a serious standard library that depends on nothing else. The trick then however is to provide packages for the various platforms that can install clojure, contrib and all of its dependencies so a user that's not interested in hacking on the clojure or contrib source can just get up and running with minimal fuss. That still leaves open the question of how to decide which third party libraries are OK to include as a dependency. That seems to require a more formal process similar to the PEP's in Python. Maybe it's too early for something like that though. -- Cosmin Stejerean http://offbytwo.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
