> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
> 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 met
> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
> 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 met
On Wed, 6 Mar 2024 15:31:40 GMT, Chen Liang wrote:
> Looking at 8326836 #18030, we might need `@since` tags on the new API methods.
Thanks for pointing it out, I've added them.
-
PR Comment: https://git.openjdk.org/jdk/pull/17282#issuecomment-1981230434
> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
> 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 met
On Wed, 6 Mar 2024 15:00:09 GMT, Adam Sotona wrote:
>> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
>> Existing ClassFile API use cases proved the concept one big CodeBuilder is
>> comfortable. However there are some redundancies, glitches in the naming
>> conventions,
> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
> 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 met
> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
> 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 met
On Mon, 5 Feb 2024 17:23:54 GMT, Paul Sandoz wrote:
>> Adam Sotona has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> removed CodeBuilder::newObject methods
>
> src/java.base/share/classes/java/lang/classfile/CodeBuilder.java line 507:
>
>
On Mon, 5 Feb 2024 18:31:44 GMT, Adam Sotona wrote:
>> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
>> Existing ClassFile API use cases proved the concept one big CodeBuilder is
>> comfortable. However there are some redundancies, glitches in the naming
>> conventions,
> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
> 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 met
On Fri, 5 Jan 2024 15:17:13 GMT, Adam Sotona wrote:
> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
> Existing ClassFile API use cases proved the concept one big CodeBuilder is
> comfortable. However there are some redundancies, glitches in the naming
> conventions, some
On Fri, 5 Jan 2024 15:17:13 GMT, Adam Sotona wrote:
> `java.lang.classfile.CodeBuilder` contains more than 230 API methods.
> Existing ClassFile API use cases proved the concept one big CodeBuilder is
> comfortable. However there are some redundancies, glitches in the naming
> conventions, some
`java.lang.classfile.CodeBuilder` contains more than 230 API methods.
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
ha
13 matches
Mail list logo
