<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Hello,<br>
</p>
<div class="moz-cite-prefix">On 11/22/2024 9:35 AM, Eirik Bjørsnøs
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CA+pBWhu59K54JZEXETxnPYjFhaBrJiHG4ut=uBRCT_2quVSy9A@mail.gmail.com">
<div dir="ltr">
<div dir="ltr">On Fri, Nov 22, 2024 at 4:47 AM Joseph D. Darcy
<<a href="mailto:joe.darcy@oracle.com" moz-do-not-send="true" class="moz-txt-link-freetext">joe.darcy@oracle.com</a>>
wrote:</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>PS it would be a "small matter of programming" to write
an annotation processor to find the not subclassable
public classes in the JDK that were not marked final.</p>
</div>
</blockquote>
<div>Joe, your bait was too hard to resist.</div>
<div><br>
</div>
<div>These are the non-final, not subclassable, public,
non-enum classes, in packages with unqualified exports in
java.base:</div>
<div><br>
</div>
<br>
</div>
</div>
</blockquote>
<p>[...]<br>
</p>
<blockquote type="cite" cite="mid:CA+pBWhu59K54JZEXETxnPYjFhaBrJiHG4ut=uBRCT_2quVSy9A@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>All of these compiles fine with final added. (Note a
subclass can access a private constructor if enclosed by the
same class (is this called a nest?)</div>
<div><br>
</div>
<div>What is the compatibility impact of adding final to the
above classes. It will perhaps require a CSR in any case?</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<p>Yes, these changes would require a CSR. (There would need to be
an update to the signature tests, if nothing else.)<br>
<br>
Unless there are odd circumstances, such changes are well within
our compatibility policy. (We don't mind if a program like "assert
java.lang.reflect.Modifier is not final" would fail after the
change ;-)<br>
<br>
Thanks for checking,<br>
</p>
<p>-Joe<br>
</p>
</body>
</html>