On Thu, Dec 29, 2011 at 10:50 PM, Erlis Vidal <er...@erlisvidal.com> wrote: > Cedric, you have a really good point, I just realized it after reading your > email. After sending the original email I saw what the error was, but what I > still unable to know is how could I debug from Clooj, other than using > println, any built-in trace a la LISP? > > I'm liking Clooj a lot, but really don't know how to debug there. Anyone?
I wouldn't know. I rarely need to do more than look over the code, think about it, call functions from the repl with various inputs, examine stack traces, macroexpand-1, and occasionally slip in a println or two to solve problems and find and fix bugs. Making as much stuff as possible pure functions helps a lot, because pure functions can be tested in isolation and if they work then, they work period. -- 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
