aot

AOT problem solved Thanks to the swift responses of the Clojure google group I have got past my little problem. It was, of course, deceptively simple, but not clear to someone who doesn’t do Java programming much. The problem was basically that whatever I did I could not get Clojure to recognise that the source files existed in the classpath. When you invoke java with the -jar command line option it completely ignores the classpath (both the environment variable, or the -cp argument....

Caught on a Clojure roller-coaster I was hoping to make some decent progress this weekend with my Clojure code. The plan was to port it to the new AOT model of compilation. However, my efforts have been frustrated by me not being able to get AOT working. I have posted my problem to the group, so hopefully there will be some solution soon. Clojure is developing so rapidly it’s hard to keep up, I think that’s how I got into this mess with AOT....

AOT is cool, but it breaks some of what I’ve already talked about Clojure is a young language, and as such it’s developing fast. It’s an exhilarating ride to be on, but sometime it means things I’ve written change. So, when reading my previous posts, please note that the latest revisions to Clojure include the provision of Ahead-Of-Time (AOT) compilation. This will break the compilation mechanisms I used in some of the content below....