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. However, for every new problem people are finding solutions that blow me away. This blog post details a really elegant solution to the lack of tail call optimisation for mutually recursive functions:

http://www.windley.com/archives/2008/11/tail_optimized_mutual_recursion_in_clojure.shtml