JEP 12: JVM version constraints

Alex Buckley alex.buckley at oracle.com
Tue Mar 27 22:01:40 UTC 2018


On 3/26/2018 5:17 PM, John Rose wrote:
> On Mar 26, 2018, at 4:10 PM, Alex Buckley <alex.buckley at oracle.com
> <mailto:alex.buckley at oracle.com>> wrote:
>> In the time since you posted, there has been support on this list for
>> rejecting non-zero minor versions, so enumerating actually-used
>> versions is plausible. Bear in mind that preview features are part of
>> Java SE, so the enumeration would be: (assuming preview features first
>> surface in SE 11)
>>
>> ...
>> 10   45.*, 46.0, 47.0, 48.0, 49.0, 50.0, 51.0, 52.0, 53.0, 54.0
>> 11   45.*, 46.0, 47.0, 48.0, 49.0, 50.0, 51.0, 52.0, 53.0, 54.0, 55.0,
>> 55.65535
>> 12   45.*, 46.0, 47.0, 48.0, 49.0, 50.0, 51.0, 52.0, 53.0, 54.0, 55.0,
>> 56.0, 56.65535
>>
>> Please confirm that's what you were expecting.
>
> As a source of aforesaid "support", I'll say that I'd support this also.
>
> Once we get minor version restrictions properly in place, then we can
> allocate the freed-up code points for useful purposes, such as the
> current proposal "experimental = *.65535".

Where the current proposal is "preview = *.65536", of course :-)

https://bugs.openjdk.java.net/browse/JDK-8200338 tracks the JVMS change.

Alex


More information about the jdk-dev mailing list