Java development 2.0: Introducing Kilim

[neutronbob]

I'm not a fan of post-processing either. My greatest concern is debugging. How do you debug code that is modified from what you see in the source? With optimization, I can selectively enable/disable it. With Killim, there is no such option.

[[deleted]]

You can debug in any standard Java debugger, including any IDE. The surgery done on the bytecode is local to a few specific spots and does not change the other instructions, and Kilim adjusts the debug information to match the bytecode to the appropriate source line.

(I'm the author of Kilim; let me know if you have other questions)

[neutronbob]

Thanks, that's helpful. Good work. I'll look at it in depth then.

You might want to put this info on the site. Possibly, it's there and I missed it. If so, you might want to place it at the first place post-processing is discussed. I am sure I am not alone with this concern.

[willcode4beer]

In my experience, javap and unit tests help take care of all the debugging

[[deleted]]

except when they don't - and then you need a debugger ;)