I'm not an experienced Clojure programmer, and not fully committed to functional programming, so others will probably have ... cooler, and better answers. But to me it seems that there is nothing special to this situation that has to do with functional programming. Adding code that reports on what's going on always adds clutter. It's a necessary evil sometimes. For some purposes temporary print/write statements can be deleted later, and for other purposes a debugger is indispensible. For intermittent logging--i.e. when there are only a few places in the whole program where it's needed, one option is to insert functions into the call sequence that simply return what was passed to them, but produce a side effect on a file as well. But that's extra clutter, too. (Dire does look like an interesting alternative. It's something like an ad hoc debugger.)
-- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
