On Sun, 2005-05-08 at 13:05 -0400, Henri Yandell wrote: > I like it, a bold statement :) > > So, questions to the BCEL community. > > 1) Does BCEL have use-cases over ASM? I think Eugene's statement is a > healthy, competitive one and it'd be good to hear if there's > disagreement.
I'm a committer on BCEL, though mostly in order to provide oversight/guidance as a PMC member to people who really want to work on BCEL. >From my knowledge of BCEL+ASM, Eugene is absolutely right. No-one should use BCEL for a new project. See also: http://marc.theaimsgroup.com/?l=bcel-dev&m=110299532713572&w=2 and this from me: http://marc.theaimsgroup.com/?l=bcel-dev&m=110301690425183&w=2 > > 2) If Eugene is right, > > a) are there features in the planning to give BCEL a use-case? > b) should the focus be on fixing bugs for existing users instead of > adding features that ASM has already. There are quite a few projects that currently use BCEL. I think those users should be providing patches to address issues that they encounter, and that Jakarta needs to ensure (for its own reputation) that there are enough people around to evaluate and apply these patches. This is currently an issue; there is really only one person around qualified to evaluate BCEL patches (Dave Brosius) and he hasn't been particularly active of late (no criticism intended). I would *like* to improve my understanding of BCEL to the point where I can also evaluate patches (mostly for the sake of Jakarta's reputation rather than any huge personal interest in BCEL). However various commons projects have higher priority for my time at the moment. Of course if an existing Jakarta committer wants to get stuck in and improve BCEL, that's fine by me. However I don't see any signs of that. ASM is just a better-architected product, and I don't see any great benefits in putting large amounts of work into BCEL. Note that I'm not criticising the original BCEL developers. BCEL is much older than ASM as far as I am aware, and newer projects are *supposed* to be better architected than older ones. Cheers, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
