We need to remember the class file transformation via BCEL implies the
performance degradation at load-time.
IMO using the source code like this
*static final boolean DEBUG = false;
if (DEBUG) {
// wiped away by java compiler
log("my useful log message");
}
*
will give better performance but demands the additional efforts for the
re-factoring the source code.
Thanks,
Vladimir.
On 6/1/06, Anton Luht <[EMAIL PROTECTED]> wrote:
Alexei,
I've suggested BCEL but not ASM because it is an Apache product and
its license certainly fits Harmony and the author tells that he used
BCEL before.
I've used it a couple of times and everything worked just fine. No
code corruptions ever happened. It is mentioned in Sun Developer
Network JavaOne Online Technical Sessions. Seems like it's a mature
tool (even judging by version - 5.1 :) ).
On 6/1/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote:
> 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?
--
Regards,
Anton Luht,
Intel Middleware Products Division
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
