On 4 February 2010 03:38, Konrad Hinsen <konrad.hin...@fastmail.net> wrote: > For now, I'd like to get feedback and ideas for improvements!
Hi Konrad, I like it! My initial reaction is that I will use a central dedicated ns template for convenience. One thing I've wondered about with clojure core namespaces is: (clojure.xml/parse "foo.xml") ;; works fine (xml/parse "foo.xml") ;; to do this you need to require clojure.xml as xml It is 'recommended style' to always use :as Personally I dislike the use of clojure.xml :as x => (x/parse "foo.xml") Because I want it to be recognizable as a core lib. When reading (x/parse) Ok well this is probably some custom library so I better check what it is in the ns header, and then find out what the heck it does. (xml/parse) Ok well that's probably from core, if I check the ns header I can be certain it is. I can't really force everyone to use the core libname but seeing they are so short if it were available as a default I think lots of people would go that way. So a useful ns+ feature might be for core libs to be pre-aliased in this way, and to warn or disallow :as which conflicts with core libs to prevent the reverse confusion. Disclaimer - I don't think my description is quite right but the premise is that the ceremony might be reducible. -- 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 Note that posts from new members are moderated - please be patient with your first post. 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
