Re: Runtime code generation and barriers in migrating away from JVM-interal APIs

2018-01-07 Thread Rafael Winterhalter
You are right Peter, that does work. I assumed that the module to which a package was opened automatically received the access rights for any lookup object, thanks for pointing it out to me. This makes my proposal of C obsolete. I hope that D and E are considered nevertheless! Also, thank you Vol

Re: Runtime code generation and barriers in migrating away from JVM-interal APIs

2018-01-07 Thread Peter Levart
Hi Rafael, On 01/07/18 13:10, Volker Simonis wrote: At a result, even with Java 9 being supported by many popular frameworks, a migration away from internal APIs has not yet been achieved. I would therefore like to suggest the following extensions: C) When a module opens a package, other module

Runtime code generation and barriers in migrating away from JVM-interal APIs

2018-01-07 Thread Volker Simonis
: Rafael Winterhalter Datum: So. 7. Jan. 2018 um 00:08 Betreff: Runtime code generation and barriers in migrating away from JVM-interal APIs An: Hello, I am the author of Byte Buddy and a maintainer of cglib, two of the major code generation libraries in the Java ecosystem. Both libraries are