On Fri, 17 Jul 2026 02:36:17 GMT, Chris Plummer <[email protected]> wrote:
>> The following spec edits were made (no code changes): >> - a brief value object summary in the ObjectReference overview section >> - A clarification on the difference between "value classes/objects" and the >> JDI Value class >> - Specifying where JDI ignores strict field initialization rules. >> >> The JBS issue contains screenshots of the rendered relevant javadoc. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Chris Plummer has updated the pull request incrementally with one additional > commit since the last revision: > > Value is an interface, not a class I see this has already been integrated but it is problematic to use "If preview features are enabled" in the JDI spec without clarifying that it means preview features in the target VM are enabled. Whether preview features are enabled or not in the current VM is not really relevant. It gets more complicated when the JDK version used for the front-end (JDI) is different to the JDK version in the back-end (target VM), and more complicated again once JDI is "upgraded" or copied into the JDK used by the IDE/debugger. It's a similar discussion to that in JDK-8387726 which is why we decided that the simplest is for StackFrame.thisObject to link to Class.isValue instead of "If preview features are enabled". ------------- PR Comment: https://git.openjdk.org/valhalla/pull/2639#issuecomment-5021253129
