As some of you know, I suffer from a seemingly interminable obsession
with improving the Clojure debugging story.  It just seems so clear to
me that Clojure deserves a world class debugger, one befitting it's
power, beauty and elegance.  Maybe one day, we'll get there.  Till
then, here are my latest improvements to the CDT:

1. Stepping
2. Line number breakpoints
3. An Emacs based front end which allows you to: step, set
breakpoints, catch exceptions, eval remote clojure expressions, and go
up and down the stack, in a much more natural way than with just the
command line.

When you want to eval the s-expr under the cursor, hit ^x^a^p!

CDT will then serialize the s-expr, send it to the remote vm, evaluate
it there in the context of the current stack frame, and display the
result on the mode line.

Ridiculously long instructions on how to use it are here:
http://georgejahad.com/clojure/emacs-cdt.html

I should emphasize that there is nothing Emacs specific about the
CDT.  In fact, I've been so spoiled by Clojure, I don't even enjoy
writing Elisp any more.  This front end was written in Emacs because
that's the IDE I'm most familiar with.  The CDT command line is IDE
agnostic; it should be easy, (dare I say fun?), to port it to other
IDE's.  If there's interest, I'll detail how in a future post.

Many thanks to Fogus for the kind words, and to the Runa gang for
their continuing encouragement!

-- 
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

Reply via email to