Hi, On Jan 22, 2:14 am, ajay gopalakrishnan <ajgop...@gmail.com> wrote: > I usually debug by adding println statements.
if you use Emacs is this statement is true for other programming languages, too, you might be interested in using lldebug. I'm pretty sure, that when you ask the author to add support for Clojure he will. See http://www.cbrunzema.de/download/ll-debug/ll-debug.el > How can I achieve the same > effect in Clojure. I don't think I can introduce println at arbitrary places > to figure out at which step is the algorithm failing. I'm with you here. I'm almost sure, I've come across situations in which *out* must have been bound to something else, if you are using Emacs/Slime make sure to search the buffer *inferior-lisp* for missing output. Coming from Common Lisp and Slime I'm rather used to do all my debugging in Emacs and Slime, too. Really. That stacktrace-explorer is really good. However, I think that Rich Hickey thinks the Java debugging tools should be used with Clojure, too. No need to code something like that, right now, Clojure is just too young. I haven't tried them yet, but will in the near future. Probably YourKit. Maybe you want to go that way, too? Kind regards, Stefan -- 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
