>>> 3) Unless you plan on staying strictly AOT, and igoring the REPL, then >>> we're going to need a JIT, that's not exactly something you can hack >>> together in an afternoon >> >> I don't follow. > > With a AOT compiler like this project, you don't have the ability to > play at a repl. I guess if you don't want that, then that's not a > problem.
There are two REPL options, both of which I consider possibilities for debugging purposes, but not for production: * A Clojure interpreter (in Clojure). This would be useful in and of itself. * Dynamic code loading. This is kinda how ClojureScript does it. >> We already have two first class JITting Clojure implementations. This >> is a different project. > > We have two JITing versions of Clojure bolted onto a OOP VMs that are > optimized for imperative programming. > > I agree that this is a different project. And I hope it succeeds. I shall do my best :-) Mark -- 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
