> I think there should be a book on Clojure. Not a book on how to use Clojure > but a book on how Clojure was built. Somebody should be able to actually > build their own Clojure at the end of it. There is no reason why they should > do this and this is not the purpose of the book. The most important purpose > of the book would be give people confidence in Clojure. >
I second that: knowing 1) how to emit JVM bytecode and 2) why the specific data structures were chosen (refs, vars, agents) wrapped in explanations and examples for transactional memory and multithreaded environments ... that would be just the book I'd like to read right now. Albert -- Albert Cardona http://www.mcdb.ucla.edu/Research/Hartenstein/acardona --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
