- Mail original -
> De: "David Holmes"
> À: "Remi Forax"
> Cc: "core-libs-dev"
> Envoyé: Lundi 30 Novembre 2020 13:44:32
> Objet: Re: Why having the wrong InnerClasses attribute is an issue for the VM
> ?
> On 30/11/2020 8:04 pm, fo...@univ-mlv.fr wrote:
>> - Mail original -
On 30/11/2020 8:04 pm, fo...@univ-mlv.fr wrote:
- Mail original -
De: "David Holmes"
À: "Remi Forax" , "core-libs-dev"
Envoyé: Lundi 30 Novembre 2020 08:57:37
Objet: Re: Why having the wrong InnerClasses attribute is an issue for the VM ?
On 30/11/2020 5:08 pm, Remi Forax wrote:
- Mail original -
> De: "David Holmes"
> À: "Remi Forax" , "core-libs-dev"
>
> Envoyé: Lundi 30 Novembre 2020 08:57:37
> Objet: Re: Why having the wrong InnerClasses attribute is an issue for the VM
> ?
> On 30/11/2020 5:08 pm, Remi Forax wrote:
>> I've forgotten a cast in an
On 30/11/2020 5:08 pm, Remi Forax wrote:
I've forgotten a cast in an invokedynamic, hence a call to wrongTargetType,
but in order to create the error message, MethodType.toString(),
getSimpleName() is called and it fails because getDeclaringClass() verifies the
InnerClasses attribute.
For me
I've forgotten a cast in an invokedynamic, hence a call to wrongTargetType,
but in order to create the error message, MethodType.toString(),
getSimpleName() is called and it fails because getDeclaringClass() verifies the
InnerClasses attribute.
For me InnerClasses was just an attribute for
