Logging side-effects usually occur within a do block, or the equivalent, e.g., when, catch. For production code, I'd suggest a logging library instead of filling your code with printlns. Contrib has a logging lib that delegates to common java logging libraries, but allows for writing them in a more idiomatic way.
http://richhickey.github.com/clojure-contrib/logging-api.html On Jan 21, 5:14 pm, ajay gopalakrishnan <ajgop...@gmail.com> wrote: > Hi, > > I usually debug by adding println statements. 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. > > Thanks, > Ajay -- 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
