jdk.internal.classfile.impl

[Brian Goetz]

While there are not necessarily such plans now, you should always act as if this will happen at the worst possible time.  If you use options to relax encapsulation, you are basically signing a document that says “I will change my code whenever I have to, and I won’t complain about it.”

The tradeoff you are making here is that you are binding tightly to an implementation that has the flexibility to change.  You may get a short-term benefit, but you take on a long-term risk.  You get to make these choices, and deal with the consequences.

On Dec 1, 2024, at 4:35 PM, Mark Roberts <markro at cs.washington.edu<mailto:markro at cs.washington.edu>> wrote:

I have found some useful methods in jdk.internal.classfile.impl – such as LabelImpl::getBCI().  Are there any future plans to reorganize this package such that --add-exports java.base/jdk.internal.classfile.impl=ALL-UNNAMED will no longer work?

Thank you,
Mark

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/classfile-api-dev/attachments/20241202/9a39d210/attachment.htm>