> > I know don't feel comfortable with the notion of lib. I currently > assume that it is more or less similar to a namespace : it looks like > a namespace, it tastes like a namespace, but still does seem to be not > considered a namespace. >
I understand your pain. I am right now going through the same thought process, and do not have a satisfactory understanding myself. The myriad connections between namespaces and libraries as manifest through 'load-file', 'require', 'use', 'refer', 'load', have left me scratching my head. In the end, someone like you or I might need to publish our discoveries here (with the understanding that we are looking for feedback). I am currently going through the core.clj to understand the dependencies. I think you will find the API will stay out of date for the short term as things are fleshed out here and on the IRC channel. I thought that clojure was further along when I started a few weeks ago. Please don't mistake this last statement for a criticism. In fact, now that I see that I am in the middle of the birth of something extremely impressive, I am rather excited. The primitives and major design decisions of this language seem to be solid. It seems to be these higher level notions that are being refined as we speak. I've dug up month-old to half-year old posts on this group where people propose and implement breaking changes. The AOT compilation change came only a short time ago and seems to be the source of this particular API staleness. I've seen posts where the binding forms to most of the sequencing funcitons are fleshed out on the group and then committed. There seems to be a great willingness to allow these 'API's to gestate in contrib libraries before they are promoted to core -- after all, they're all just macros and functions in the end. I am guessing this trend will continue for the foreseeable future, and some examples, APIs and code libraries will be out of synch. Heck, a lot of the information I gleaned came from watching the movies, and even those are out of date (there is no longer a boot.clj for instance). I think the best course of action, for now, is to just read the code. Make core.clj your friend. It has deepened my understanding of the language decisions. (Still trying to grok 'libraries' though :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
