Hi Anton,
Anton Ryabtsev wrote:
I use Eclipse to generate it. So guess, it is ECJ.
Thanks for quick reply.
Ok, thanks very much for the heads up on this. I'll post a JIRA to document this problem and also act as a place holder for a fix should I ever work out how to provide one.
Just thought that if it is a matter of specific compiler does it make sense to have this Byteman assumption(and other future possible behaviour) be configured (e.g. via java agent option)?
Anton Ryabtsev wrote:
Just thought that if it is a matter of specific compiler does it make sense to have this Byteman assumption(and other future possible behaviour) be configured (e.g. via java agent option)?
Yes, if I can find a way to reimplement Byteman's analyzer so that it can avoid making this assumption then I would probably want to provide an option to enage this alternative analysis since I suspect the alternative implementation would be a lot slower. However, I don't yet know how I would implement such an alternative so it's a little speculative to consider it just now.