-
Enhancement
-
Resolution: Fixed
-
P3
-
None
j.l.classfile.CodeBuilder API consist of >230 methods.
The majority of the API methods may be split into three main categories:
- methods building low level bytecode instructions according to JVMS chapter 6.5 (aaload, aastore, aconst_null...)
- methods reconstructing individual subtypes of j.l.classfile.Instruction from given arguments (loadInstruction, storeInstruction, incrementInstruction, branchInstruction...)
- methods modeling high level code blocks (block, ifThen, ifThenElse, trying...)
Existing ClassFile API use cases proved the concept one big CodeBuilder is comfortable. However there are some redundancies, glitches in the naming conventions, some frequently used methods are hard to find and some methods have low practical use.
This enhancement would like to revisit j.l.classfile.CodeBuilder API methods, remove redundancies, fix naming conventions, highlight the most frequently used methods and remove methods with low practical use.
The majority of the API methods may be split into three main categories:
- methods building low level bytecode instructions according to JVMS chapter 6.5 (aaload, aastore, aconst_null...)
- methods reconstructing individual subtypes of j.l.classfile.Instruction from given arguments (loadInstruction, storeInstruction, incrementInstruction, branchInstruction...)
- methods modeling high level code blocks (block, ifThen, ifThenElse, trying...)
Existing ClassFile API use cases proved the concept one big CodeBuilder is comfortable. However there are some redundancies, glitches in the naming conventions, some frequently used methods are hard to find and some methods have low practical use.
This enhancement would like to revisit j.l.classfile.CodeBuilder API methods, remove redundancies, fix naming conventions, highlight the most frequently used methods and remove methods with low practical use.
- csr for
-
JDK-8323067 Revisit j.l.classfile.CodeBuilder API surface
- Closed