<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Hi Ron,<br>
</p>
<p>> <span style="white-space: pre-wrap">I think the most complete solution is for the JCK in such a case is to require the implementation to provide some script that compiles the source file and returns the class name of the top-level class that could then be used for launching </span></p>
<p><span style="white-space: pre-wrap"> Great idea. The approach might work. Let us think more in that direction.</span></p>
<p><span style="white-space: pre-wrap">> </span><span style="white-space: pre-wrap">...OR a script that compiles and then immediately runs the file.</span></p>
<p><span style="white-space: pre-wrap"> The JCK runs compiled classfile with a reference JVM not with a tested JVM. Not a problem: the JCK handles those steps.</span></p>
<p><span style="white-space: pre-wrap">Thanks,
-leonid
</span><span style="white-space: pre-wrap"></span></p>
<div class="moz-cite-prefix">On 11/28/2023 11:05 AM, Ron Pressler
wrote:<br>
</div>
<blockquote type="cite" cite="mid:7B7C6CE3-0CD6-49EF-8969-09252FF431A5@oracle.com">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 28 Nov 2023, at 18:59, Leonid Arbuzov <a class="moz-txt-link-rfc2396E" href="mailto:leonid.arbouzov@oracle.com"><leonid.arbouzov@oracle.com></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Alternatively, the JCK could rely on the following from the new spec (although I don’t know to what extent that’s allowed):
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Yes, the JCK can use that typically generated class names. This might work for the most Java SE implementations. Original question was what should the JCK do for those non-typical implementations? The JCK can ask an user to provide a custom converter (source name to class name).
But this would not work for implementations that generate class names indeterministically. Hopefully there will be none or a few of such ones and the JCK can run a weaker tests for them. But a concern was that JCK users would be allowed to choose to run those weaker tests...
Can the spec somehow close this option? Or the JCK can close it on its own?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I think the most complete solution is for the JCK in such a case is to require the implementation to provide some script that compiles the source file and returns the class name of the top-level class that could then be used for launching OR a script that compiles and then immediately runs the file.
— Ron</pre>
</blockquote>
</body>
</html>