First of all, I am not the developer of Log4s, but I have been using it for a while and I see no significant gain switching to SystemLogger or ZnLogEvent. As Alain said, it is based in Log4j, which has his own Wikipedia page: http://en.wikipedia.org/wiki/Log4j

I don't think there is too much sense in having "Log Objects" around, where probably I want to tail a daily rolled log from a headless remote image. I read the documentation of SystemLogger hoping to find a mechansim which dynamically selects compression strategies based in what's logged, or some other advanced feature, but I didn't found any :(

So if Object logging is implementing #asLog and #logClass methods maybe I should add them so Log4s can log "Object" :). But seriously, such comparison is not fair. Let's compare real logging features: priorities, levels, appenders, output destinations, hierarchical logging, formatting layout, etc. Many of them are implemented in Log4s.

Cheers,

Hern��n

2015-01-12 14:56 GMT-03:00 Sven Van Caekenberghe <sven@stfx.eu>:

> On 12 Jan 2015, at 18:27, Alain Rastoul <alf.mmm.cat@gmail.com> wrote:
>
> hi all,
>
> Googling a bit for a logging framework in Pharo, I found sl4j, which sounds�� familiar to me.
> http://ss3.gemstone.com/ss/Log4s.html/Wiki
>
> I suppose the API is the same as the java package, as claimed by the project page.
> I wonder if anybody is using it , or has tried it and have an advice on that package ?
> (I�� saw there was no test and no comments ... :( )
>
> I think it could be great for Pharo to have a standard package like that, a logging facility is mandatory for most -if not all- applications
>
> Any advice or pointers ?

Object logging instead of String logging is the way to go. SystemLogger, Beacon, Zinc's ZnLogEvent are examples. Search the mailing list for past discussions.

> TIA
> --
> Regards,
>
> Alain
>
>