That's very plausible, and your thoughts on intermediate representations are quite interesting. Now I'm going to change the subject back to my tangent. :)
Maybe it wouldn't be so "really, really hard to debug when Lisp's stack and your DSL's get intertwined in a complex way in your stack trace" if Lisp stack traces weren't so hard to debug in the first place. At least, they are for me. If anyone has any hints, please chime in. I'm getting tired of BREAK-and-FORMAT-driven-debugging. When Visual Studio does anything better than a Lisp environment, that's a goddamn emergency.
In the meantime, I think I'm going to try Clozure-with-a-Z and see if life is better.
p.s. If you do write a blog about this stuff, post it here. I'll read it.
Comments
That's very plausible, and your thoughts on intermediate representations are quite interesting. Now I'm going to change the subject back to my tangent. :)
Maybe it wouldn't be so "really, really hard to debug when Lisp's stack and your DSL's get intertwined in a complex way in your stack trace" if Lisp stack traces weren't so hard to debug in the first place. At least, they are for me. If anyone has any hints, please chime in. I'm getting tired of BREAK-and-FORMAT-driven-debugging. When Visual Studio does anything better than a Lisp environment, that's a goddamn emergency.
In the meantime, I think I'm going to try Clozure-with-a-Z and see if life is better.
p.s. If you do write a blog about this stuff, post it here. I'll read it.
You can debug Clojure-with-a-J code using JSwat. http://clojure.org/getting_started#toc5
Heh. That comes from the old Kids in the Hall characters Cathy-with-a-C and Kathy-with-a-K.
I'm probably not going to use Clojure any time soon, though am following it at a distance.