Hi John,
ummm ... this seems to imply I can remove the findSuperConstructor() proposal
from the Indy JEP. Incidentally, it's on my list for this week - and less work
is always good. ;-) Even if, in this case, it leads to disappointment. I agree
with you in that opening up the MH API like this w
On Aug 29, 2015, at 4:42 AM, Jochen Theodorou wrote:
>
> hi John,
>
> thanks for replying...
>
> After having read that, I think part of the problem actually comes from this
> new-invokespecial-super being split in two bytecodes. It means there can be a
> lot of things in between, including d
On Sep 17, 2015, at 10:10 AM, Michael Haupt wrote:
>
> ummm ... this seems to imply I can remove the findSuperConstructor() proposal
> from the Indy JEP. Incidentally, it's on my list for this week - and less
> work is always good. ;-) Even if, in this case, it leads to disappointment. I
> agr