harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Zakharov" <alexei.zakha...@gmail.com>
Subject Re: [classlib] logging from within our implementation
Date Thu, 01 Jun 2006 09:48:49 GMT
As far as I understand they use ObjectWEb ASM rather than BCEL in
their example. But in any case, this approach implies trust in these
code-manipulation libraries. Does it stable enough? Can't it produce
corrupted byte-code?

2006/6/1, Geir Magnusson Jr <geir@pobox.com>:
> Anton Luht wrote:
> > It is possible to remove all calls to logging below a certain level
> > from .class files using BCEL:
> > http://surguy.net/articles/removing-log-messages.xml . In this example
> > logging is removed on fly when class is loaded, but this tool can be
> > run against class files in the process of building release version.
> > For example, debug version can contain all logging and release - only
> > errors. This approach has one disadvantage: it is non-standard and
> > looks like a dirty hack :)
> Yah.  I'd rather see us add the logging this way rather than removing
> it, using annotations or aspects or something... I'll try to experiment
> with this tomorrow.

Alexei Zakharov,
Intel Middleware Product Division

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message