A list of issues about Classfile API
Brian Goetz
brian.goetz at oracle.com
Wed Jun 28 15:37:31 UTC 2023
Thanks, Adam, this is a good point. All the more reason why we need
some better documentation on attribute handling, and especially on
"special attributes"; not only are some attributes (e.g.,
BootstrapMethodsTable) treated specially, here StackMapTable can be
treated either way.
On 6/28/2023 11:33 AM, Adam Sotona wrote:
>
> *From: *classfile-api-dev <classfile-api-dev-retn at openjdk.org> on
> behalf of liangchenblue at gmail.com <liangchenblue at gmail.com>
> *Date: *Wednesday, 28 June 2023 8:33
> *To: *classfile-api-dev <classfile-api-dev at openjdk.org>
> *Subject: *A list of issues about Classfile API
>
> Hello, I just looked over the Classfile API and found a few design
> issues, aside from simple typos addressed in
> https://github.com/openjdk/jdk/pull/14686:
>
> Specific issues:
>
> 1.1. If CodeElement is only for streamable elements, then
> StackMapTableAttribute shouldn't be a CodeElement, as it's never
> delivered in code streams.
>
> StackMapTableAttributeis not delivered, however there is a strong case
> where user needs to create it manually and drop to CodeBuilder (with
> generation disabled).
>
> We probably forgot about this case and it is not tested, however it
> should work.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/classfile-api-dev/attachments/20230628/56e23d97/attachment-0001.htm>
More information about the classfile-api-dev
mailing list