<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 25/11/2022 13:27, Ethan McCue wrote:<br>
<blockquote type="cite" cite="mid:CA+NR86hZOAKEe-aq13SX0L7XSerC8gBeZ7AyvmiFnFpfq48Srg@mail.gmail.com">
<div dir="ltr">...huh <br>
<br>
<pre style="color:rgb(0,0,0)">>><span style="font-family:Arial,Helvetica,sans-serif"> </span>The recent removal of Nashorn has indicated several places were
>> javascript were used in the JDK mainly due to it's built-in support for
>> parsing JSON<i>
</i><font face="arial, sans-serif">None of those seem like they would have been using nashorn in the past, so i wonder what this is referring to.</font></pre>
</div>
</blockquote>
<br>
The quoted text seems to be from a mail that Magnus Ihse Bursie sent
to the discuss list in 2020 [1]. It's the same date that JDK-8242934
[1] was created so it may be that the mail was (at least partly)
prompted by the need to change the test for`jfr print --json`. The
test for that feature used to use Nashorn and had to be changed to
use a JSON parser in the test suite. The JSON parser was
subsequently moved to test/lib/jdk/test/lib/json/JSONValue.java so
it could be used by other tests.<br>
<br>
-Alan<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://mail.openjdk.org/pipermail/discuss/2020-April/005398.html">https://mail.openjdk.org/pipermail/discuss/2020-April/005398.html</a><br>
[2] <a class="moz-txt-link-freetext" href="https://bugs.openjdk.org/browse/JDK-8242934">https://bugs.openjdk.org/browse/JDK-8242934</a><br>
</body>
</html>