> On 19 Jun 2017, at 18:28, John Rose <john.r.r...@oracle.com> wrote: > > On Jun 9, 2017, at 1:51 PM, John Rose <john.r.r...@oracle.com> wrote: >> >> We have talked about "condy" (a constant-pool friend for indy). >> Enclosed is the javadoc portion of a draft spec. >> The JVM spec. is not ready and will be sent separately. >> This javadoc reflects code checked into the condy branch of Amber. > > I have updated the javadoc portion of the spec for constant-dynamic. > There are small but strategic changes to MethodType and MethodHandle, > as well as new classes to represent the "pull mode" of constant resolution. > The key changes relevant to the JVM are in package-info.html, > and (of course) in the forthcoming JVM spec. changes. > > http://cr.openjdk.java.net/~jrose/jvm/specdiff-condy-2017-0619.zip >
package-summary — "Bytecode may contain dynamic call sites equipped with equipped with bootstrap methods" s/equipped with equipped with/equipped with/ "This allows the bootstrap logic the ability to order the resolution of constants and catch linkage exceptions.” And possibly still link a constant rather than re-throwing a linkage exception? "The second-to-last example assumes that all extra arguments are of type CONSTANT_String” s/CONSTANT_String/String BootstrapCallInfo — "This information include the method” s/include/includes Paul. > (I've given up sending attachments for now since the server > scrubs them.) > > — John
