On Thu, 2011-09-08 at 08:38 +0300, Pekka Enberg wrote: > I started hacking on invokedynamic again: > > https://github.com/penberg/classpath/commit/21c457f4928678bb5709dfc5a992b80f0d02c4b8 > > https://github.com/penberg/jato/commits/indy > > I'm planning to use ASM for generating bytecode for method handle > chains. Does that sound like a reasonable thing to do? We already > carry the ASM code under tools/external/asm/. Can I just move that > under external/ and rename the package so that it doesn't clash with > the upstream project? Under tools it really is just the upstream code as is to make building easier (and IMHO we should have at least a configure switch like --with-antlr-jar to just use the system one). If we move it into the core runtime library and munge/rename it we should also come up with a way to maintain and upgrade it ourselves. I don't know much about what is needed for invoke dynamic byte code generation. Note that java/lang/reflect/Proxy.java for example also can generate byte code, but just does it by hand. Is such an approach possible? Thanks, Mark
