As of Build 142, I changed the way that logging works in the node and client.

Rather then a static method in the support.Logger class being called, you
should now call an implementation of Logger attached as Core.logger. It's
interface has also changed, instead of sending a string with the filename
(which was really annoying because everyone copied code without changing the
names), send "this" and it will call this.getClass().getName() (if code is
static ask yourself if it should be, and then send null). I also added a
verbosity 5 where the object's hashcode gets output as well, and 6 where it
does a stacktrace on every log call.

So instead of

Logger.log("foo/bar.java","O Solo Mio!",Logger.NORMAL):

write this

Core.logger.log(this,"O Solo Mio!",Logger.NORMAL);

I fixed all the logger calls in the Freenet code (all 222 of them). I
apologize to client authors who now have broken builds, but it isn't exactly
hard to fix. I think this is better since it will allow people to easily plug
in a graphical logger, or an XML log, or an email log, or whatever, without
having to parse the outputstream.

-- 
\oskar

_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev

Reply via email to