On 14 February 2010 14:40, Jeppe Nejsum Madsen <[email protected]> wrote:
> Hi,
>
> I've tried to keep it as simple as possible, really just a Scala layer
> on top of the SLF4J api.
>
I think that's a very good decision!
> Note that no backend (log4j or logback) configuration is included. This
> has to go into lift-util to use runmode etc.
>
> You can have your choice of a nested logger:
>
> object MyObj extends Logging {
> logger.info("nested Hello")
> }
>
> or direct access:
>
> object MyObj extends Loggable {
> info("direct Hello")
> }
>
> Thoughts?
>
I really like to have Logging and Loggable, but I would call them vice versa
and change Logging to Logger. As an example think of Iterable and Iterator.
In general an Xable gives you access to an X. Hence we should have Loggable
with a method logger that returns a Logger and we should have Logger to mix
in all the logging methods. Why change from Logging to Logger? Because we
should call it what it is, not what it does.
Cheers,
Heiko
Work: weiglewilczek.com
Blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: scalamodules.org
Lift, the simply functional web framework: liftweb.net
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
