On Mon, Jun 2, 2008 at 5:17 PM, Rémi Forax <[EMAIL PROTECTED]> wrote:
> > Hi all, > I've just pushed a new implementation of the backport. > CallSites are now created dynamically as needed and can be garbaged > if there are no longer used. Excellent! I am working on my backlog and will get to the point where I get to play with the backport in a week or two. Really looking forward to it. > > > I've planned to release two tools. > - one that can be used at compile time, just after your compiler > or as last step of the compilation (using ASM adapters). > - A java.lang.instrument agent that modifies the bytecode > at runtime when it is loaded. Sounds like a nice approach. > > > I've some questions about the language runtime you implement : And I have some answers about Jython. > > 1) Do you use another library than ASM to generate bytecodes ? We have a legacy compiler that doesn't use ASM, but in the cases that this backport would be interesting, it's all ASM. > > 2) Do you generate bytecodes at runtime ? Yes. > > - Do you use your own classloader ? Sometimes. > > - Do you use java.lang.instrument ? Not at the moment, but we are experimenting with it and might use it in the future. regards, Tobias --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
