Hi Alex, You've got my vote - logging is essential for non-trivial programs.
Your implementation is superior to mine, but maybe you would like to include some sub-parts: http://github.com/timothypratley/strive/blob/baf83e2bb26662f5f5049d165dec31e47b91e171/clj/timothypratley/logging.clj log-capture -> grabs normal prints if any are left in the code log-format -> better output for java.logging logged-future -> I find handy for long running threads debug -> its nice to be able to log an expression and what its evaluated to while leaving it in place (+ (debug (+ 1 2)) 3) current-function-name (Stephen C. Gilardi posted) -> optionally including the function and thread id Regards, Tim. On Jul 22, 3:13 pm, ataggart <alex.tagg...@gmail.com> wrote: > I've written up a small set of logging functions to output from > clojure what I'm already doing from my production java code. > > Currently it checks for the presence of commons-logging, log4j, and > finally java.util.logging. The clojure code doesn't actually do any > logging itself; instead everything is delegated to whatever you've > been using all along. > > I've stuck the code athttp://paste.lisp.org/display/83982 > > I'd welcome any thoughts, particularly if this merits going into > clojure-contrib. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
