Just a reminder that logging has moved to it's own repository in the
clojure space. It can be found at
http://github.com/clojure/tools.logging
and is where all future development of the library should exist. If you
would like to submit patches for logging, please do so against the new
project instead of contrib.
--
Cheers,
Aaron Bedra
--
Clojure/core
http://clojure.com
On 04/10/2011 10:48 PM, Paul Legato wrote:
Hi,
I'd like to suggest two enhancements to clojure-contrib.logging:
1) There should be an easy way to set the current log level threshold
(DEBUG, WARN, etc.) I've written two set-log-level! functions which do
this, at http://www.paullegato.com/blog/setting-clojure-log-level/ .
I'm not sure why some Clojure instances return a
org.apache.commons.logging.impl.Jdk14Logger and others a
java.util.logging.LogManager$RootLogger from (impl-get-log "").
Perhaps there's a better / more universal way to write the log level
setting function than this?
2) The logging/spy macro doesn't print lazy sequences to the log;
instead, it prints something like "clojure.lang.LazySeq@8592". Since
the user has explicitly requested that the sequence's value be logged,
it makes sense to me to run the sequence and log the result. I've
implemented this at
http://www.paullegato.com/blog/lazy-spy-clojure-logging-lazy-sequences/.
Again, I'm not sure if this is the best way to go about it.
Suggestions or improvements would be greatly appreciated.
Best,
Paul
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
