On Tue, 29 Apr 2025 19:17:02 GMT, Chen Liang wrote:
>> Some AccessFlag parsing methods throw IAE because a flag mask is not valid
>> in a location. However, there is no easy way to check what flag mask bits or
>> what flags are valid for a location. We need such APIs to check, specific to
>> e
On Tue, 29 Apr 2025 19:17:02 GMT, Chen Liang wrote:
>> Some AccessFlag parsing methods throw IAE because a flag mask is not valid
>> in a location. However, there is no easy way to check what flag mask bits or
>> what flags are valid for a location. We need such APIs to check, specific to
>> e
On Tue, 29 Apr 2025 19:10:17 GMT, Chen Liang wrote:
>> src/java.base/share/classes/java/lang/reflect/AccessFlag.java line 38:
>>
>>> 36: import java.lang.classfile.attribute.ModuleRequireInfo;
>>> 37: import java.lang.module.ModuleDescriptor;
>>> 38: import java.util.*;
>>
>> Wildcard imports a
On Tue, 29 Apr 2025 18:49:58 GMT, Roger Riggs wrote:
>> Chen Liang has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Update specs for other existing APIs
>
> src/java.base/share/classes/java/lang/reflect/AccessFlag.java line 38:
>
>> 36:
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
On Mon, 28 Apr 2025 22:07:00 GMT, Chen Liang wrote:
>> Some AccessFlag parsing methods throw IAE because a flag mask is not valid
>> in a location. However, there is no easy way to check what flag mask bits or
>> what flags are valid for a location. We need such APIs to check, specific to
>> e
On Tue, 29 Apr 2025 18:40:51 GMT, ExE Boss wrote:
>> Hmm, I intentionally avoided implementing spliterator because there are too
>> many opportunities to optimize - a fully optimized Spliterator implementaton
>> should split an int mask. Can we do that in another patch? I need to check
>> if M
On Sun, 27 Apr 2025 17:29:32 GMT, Chen Liang wrote:
>> src/java.base/share/classes/java/lang/reflect/AccessFlag.java line 722:
>>
>>> 720: }
>>> 721:
>>> 722: private static final class AccessFlagSet extends
>>> AbstractSet {
>>
>> This should probably also define the spliterator meth
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
On Mon, 28 Apr 2025 21:48:40 GMT, Roger Riggs wrote:
>> Chen Liang has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Wording updates, thanks Roger
>
> src/java.base/share/classes/java/lang/reflect/AccessFlag.java line 342:
>
>> 340: /
On Mon, 28 Apr 2025 20:20:28 GMT, Chen Liang wrote:
>> Some AccessFlag parsing methods throw IAE because a flag mask is not valid
>> in a location. However, there is no easy way to check what flag mask bits or
>> what flags are valid for a location. We need such APIs to check, specific to
>> e
On Mon, 28 Apr 2025 20:20:28 GMT, Chen Liang wrote:
>> Some AccessFlag parsing methods throw IAE because a flag mask is not valid
>> in a location. However, there is no easy way to check what flag mask bits or
>> what flags are valid for a location. We need such APIs to check, specific to
>> e
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
On Mon, 28 Apr 2025 19:56:23 GMT, Roger Riggs wrote:
>> Chen Liang has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Fix iterator missing NSEE
>
> src/java.base/share/classes/java/lang/reflect/AccessFlag.java line 634:
>
>> 632:
On Sat, 26 Apr 2025 19:44:02 GMT, Chen Liang wrote:
>> Some AccessFlag parsing methods throw IAE because a flag mask is not valid
>> in a location. However, there is no easy way to check what flag mask bits or
>> what flags are valid for a location. We need such APIs to check, specific to
>> e
On Sun, 27 Apr 2025 16:47:59 GMT, ExE Boss wrote:
>> Chen Liang has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Fix iterator missing NSEE
>
> src/java.base/share/classes/java/lang/reflect/AccessFlag.java line 722:
>
>> 720: }
>> 721
On Sat, 26 Apr 2025 19:44:02 GMT, Chen Liang wrote:
>> Some AccessFlag parsing methods throw IAE because a flag mask is not valid
>> in a location. However, there is no easy way to check what flag mask bits or
>> what flags are valid for a location. We need such APIs to check, specific to
>> e
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
On Fri, 18 Apr 2025 17:39:05 GMT, Chen Liang wrote:
>> Some AccessFlag parsing methods throw IAE because a flag mask is not valid
>> in a location. However, there is no easy way to check what flag mask bits or
>> what flags are valid for a location. We need such APIs to check, specific to
>> e
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
> Some AccessFlag parsing methods throw IAE because a flag mask is not valid in
> a location. However, there is no easy way to check what flag mask bits or
> what flags are valid for a location. We need such APIs to check, specific to
> each class file format version.
>
> Also in the investigat
Some AccessFlag parsing methods throw IAE because a flag mask is not valid in a
location. However, there is no easy way to check what flag mask bits or what
flags are valid for a location. We need such APIs to check, specific to each
class file format version.
Also in the investigation, it's no
26 matches
Mail list logo
