On Mon, 17 Jun 2024 13:55:50 GMT, Chen Liang wrote:
>> `javap` should never silently ignore erroneous class file content.
>> If the flag value violates JVMS - it should be reported as an error and
>> `javap` should reflect that in the return value.
>> On the other hand `javap` should handle such
On Mon, 17 Jun 2024 09:19:22 GMT, Adam Sotona wrote:
>> Chen Liang has updated the pull request incrementally with two additional
>> commits since the last revision:
>>
>> - I am a dumbass
>> - Retain strict flag for Method, even though it's obsolete
>
> `javap` should never silently ignore e
On Fri, 14 Jun 2024 17:02:40 GMT, Chen Liang wrote:
>> Currently, javap crashes for class files that have set non-zero values for
>> undefined access flag bits, as
>> `java.lang.reflect.AccessFlag.maskToAccessFlag` and
>> `java.lang.classfile.AccessFlags.flags` fail. In contrast, the JVMS, tho
> Currently, javap crashes for class files that have set non-zero values for
> undefined access flag bits, as
> `java.lang.reflect.AccessFlag.maskToAccessFlag` and
> `java.lang.classfile.AccessFlags.flags` fail. In contrast, the JVMS, though
> asking for these bits to be set to 0, requires VM t