Log4CL

Log4CL homepage: http://common-lisp.net/project/log4cl/

Alternatives:

• Arnesi has a logger that has separate compile time and runtime log levels with macros, and has a slime-repl-appender that prints inspectable presentations of the log parameters in the Slime repl. (Logging is planned to be factored out from Arnesi)

Feedback (Jul 2006)

Dan Weinreb? as a word about Log4j in his Lisp for High-Performance Transaction Processing google talk (at about ??:?? IIRC it's in the second half, please update the time if you watch it).

Good: It compiles on recent SBCL (with a lot of performance related notes)

Bad1: everything is done via defclass and generic functions, which may probably affect performance when having a lot of log-debugs..

Bad2: log-debug etc are generic functions and not macros. It means that if you have a lot of log-debugs, even if debug logging is disabled, then all the parameters to log-debug are still evaluated, killing performance.

Bad3: config.lisp is unfinished (not included into .asd but is in CVS), depends on unknown package cl-ini (for parsing Java .properties style config files), therefore no configuration with log4cl.properties or such is available

Bad4: I'm probably the only person who checked out this package in the last 2 years, since Google can find no feedback whatsoever on it.

Conclusion: Needs rewrite or replacement.

Replacement : log5

This page is linked from: Log framework  

CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively