Details
-
Enhancement
-
Status: Resolved
-
P4
-
Resolution: Fixed
-
17
-
None
Description
With the possibility of a bit position being reused in the same kind of construct for different purposes on different class file versions (
As a straw man proposal:
- core reflection classes get a new "modifiers" method which returns an enum set of modifiers
- the modifiers enum has a constant for each modifier. A modifier can include information such as its bit position, what kinds of constructs it is applicable to (classes, fields, methods, etc.), string representation, etc.
This would allow bit positions with collisions, such as var-args and transient, to be modeled appropriately.
Such a class would be analogous to javax.lang.model.element.Modifier.
Attachments
Issue Links
- csr for
-
JDK-8281660 Better modeling of access flags in core reflection
-
- Closed
-
- relates to
-
JDK-8289106 Add model of class file versions to core reflection
-
- Resolved
-
-
JDK-8286101 Support formatting in @value tag
-
- Resolved
-
-
JDK-8291360 Create entry points to expose low-level class file information
-
- Resolved
-
-
JDK-8291734 Return accurate ACC_SUPER access flag for classes
-
- Resolved
-
-
JDK-8292576 Improve wording of AccessFlag-related specs
-
- Resolved
-
-
JDK-8281766 Update java.lang.reflect.Parameter to implement Member
-
- Closed
-
-
JDK-6354476 (reflect) {Method, Constructor}.toString prints out inappropriate modifiers
-
- Resolved
-
-
JDK-8297271 AccessFlags should be specific to class file version
-
- Resolved
-
-
JDK-8296950 [lworld] AccessFlags should be specific to class file version
-
- Resolved
-
-
JDK-8145048 consider enhancements to EnumMap and EnumSet
-
- Open
-
-
JDK-8287330 (valhalla) Better modeling of access flags in core reflection
-
- Resolved
-
-
JDK-8266524 javac changes for JEP 306
-
- Closed
-