Alyssa Kwan <alyssa.c.k...@gmail.com> writes: > Perfect! That makes things so much easier! I assume that interning > vars is synchronized then? This is the second big source code read > FAIL in two days. Obviously I can't read. :)
They're stored in an AtomicReference (basically an atom). > All persistence requires dealing with migrations and compatibility. > That's not a reason not to persist. What are needed are good tools/ > idioms for dealing with it. ORM has succeeded on that front because > the data is arbitrarily readable and writeable with standard tools, so > the engineer can always manually modify stuff to migrate it. If a > Clojure object data store were arbitrarily readable and writeable, > then this is the first step to solving the problem. The second step > is Ruby-style migrations. Fair enough, I'm looking forward to seeing what you come up with. :-) > Because it's not at compile time, I don't have access to the expr that > generates the function. Stuart Halloway mentioned an invoke-time > check for recompilation, which I assume requires the function to hang > onto the expr and lexical environment which generates it. AFAICT, > there is no such reference, and invoke-time lookups through vars are > still being used; I'm probably not looking in the right place. I can't find something like that either and I can't see why it would exist. Perhaps he was talking about JIT recompilation, not source recompilation? -- 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
