On Jul 12, 2009, at 4:41 PM, Morgan Allen wrote:
Fair enough. However, what I had in mind was that I could simply compile one namespace that would then act as a sort of 'bootstrap loader' for other clojure source, so that I wouldn't have to recompile manually all the time.
Rayne's suggestion is a good one.What is your development workflow that requires frequent manual recompilation? All Clojure source code is compiled "just in time" as it's being loaded and before it's run. What "ahead of time" compilation gets you is faster loading times and the ability to deploy in a "class file only" environment. There is no runtime speed difference between code that was compiled using "compile" and code that was loaded via "require" or "use" or "load", even at the REPL.
Speaking of which- is it possible to access the REPL directly from within java?
What piece of your current way of launching the REPL are you hoping to avoid? If you're talking about communicating with a REPL from an existing (say GUI) application, see clojure.contrib.server-socket which includes a REPL you can communicate with over a socket. There are also ways to invoke Clojure code from Java. A Google search for: | call clojure from java | turns up some good results.
--Steve
smime.p7s
Description: S/MIME cryptographic signature
