On May 6, 2009, at 4:03 AM, Fredrik Öhrström wrote: > The bytecode verifier also prohibits calling a constructor on an > already > initialized reference. With a MethodHandle to a constructor it would > be > possible violate this restriction. I am not sure this is a good idea.
You're right in being skeptical. Basically, the only places you can use it is where the superclass constructor has already been called. Calling a superclass constructor a second time is always just wrong. We'll yank it, until & unless we find a usage pattern that actually makes sense. Thanks! -- John _______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
