-
Enhancement
-
Resolution: Fixed
-
P4
-
14
-
b20
Improve JVM handling of well known type signature characters by defining such characters in classfile_constants.h and consistently using those definitions throughout the JVM when parsing signatures.
For example add:
enum {
JVM_SIGNATURE_ENDPACKAGE = '/',
JVM_SIGNATURE_ENDPACKAGE_DOT = '.',
JVM_SIGNATURE_SPECIAL = '<',
JVM_SIGNATURE_ENDSPECIAL = '>',
In addition use more consistently already existing definitions such as:
JVM_SIGNATURE_ARRAY instead of checking explicitly for '['
JVM_SIGNATURE_CLASS instead of checking explicitly for 'L'
JVM_SIGNATURE_ENDCLASS instead of checking explicitly for ';'
For example add:
enum {
JVM_SIGNATURE_ENDPACKAGE = '/',
JVM_SIGNATURE_ENDPACKAGE_DOT = '.',
JVM_SIGNATURE_SPECIAL = '<',
JVM_SIGNATURE_ENDSPECIAL = '>',
In addition use more consistently already existing definitions such as:
JVM_SIGNATURE_ARRAY instead of checking explicitly for '['
JVM_SIGNATURE_CLASS instead of checking explicitly for 'L'
JVM_SIGNATURE_ENDCLASS instead of checking explicitly for ';'
- relates to
-
JDK-8193071 Revisit if classfile_constants.h should be removed from exported header files
-
- Open
-
-
JDK-8230199 consolidate signature parsing code in HotSpot sources
-
- Resolved
-