United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6868539 javap should use current names for constant pool tags
JDK-6868539 : javap should use current names for constant pool tags

Details
Type:
Bug
Submit Date:
2009-08-05
Status:
Closed
Updated Date:
2012-01-13
Project Name:
JDK
Resolved Date:
2012-01-13
Component:
tools
OS:
generic
Sub-Component:
javap
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:

Related Reports

Sub Tasks

Description
javap currently uses the somewhat obscure and inappropriate name "Asciz" to identify Utf8 entries in the constant pool, and inconsistent names for the rest, sometimes java names, sometimes something close to the JVMS name, sometimes exactly the JVMS name.

This should be rationalized.

                                    

Comments
EVALUATION

Recently, the provenance of Asciz has become clear.  Constant pool entry type 1 used to be CONSTANT_Asciz (or CONSTANT_Asciiz, depending where you read) and Constant pool entry type 2 used to be CONSTANT_Unicode. Both names date from around 1995 and JDK 1.0.    By the time of JVMS 1st edition, constant pool entry types 1 and 2 had been combined into CONSTANT_Utf8, value 1, with 2 being unused.

The suggested name for all tag entries is the JVMS name, without the leading CONSTANT_
                                     
2009-08-05



Hardware and Software, Engineered to Work Together