Clojure is saving our life and enabling thing we would never have dreamed of without in our ARIES project (http://ecoinformatics.uvm.edu/ aries). Still, we need to hack RT in order to be able to use it. I've seen some discussion on classloader flexibility in the context of Eclipse integration. In our case, we use a similar environment (JPF plugin framework, may move to similar OGSI later) where Clojure bindings are loaded by each plugin in sequence, each having to use a specific classloader in order to see the Java classes in the plugin. Because there is one RT, we're not going to make it work unless we manually switch the classloader Clojure uses to the plugin-specific one every time we load bindings. This requires making a field public and it's, generally speaking, a ugly hack. Also, because we run in a multi-user server environment, we'd love to have one RT per session so we could only load what's needed there and not pollute the runtime in other sessions. Or even RT objects arranged in a tree so each can use the parent's environment and cleanly be disposed of when not needed anymore.
All this is clearly hard to do with the current static Clojure runtime. How much of this is a choice, and how much is likely to change in the future? We'd love to use Clojure as is. Otherwise, thanks, thanks, thanks.... ferdinando http://ecoinformatics.uvm.edu http://www.integratedmodelling.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
