https://saxonica.plan.io/https://saxonica.plan.io/favicon.ico2022-08-27T23:24:08ZSaxonica Developer CommunitySaxon - Support #5665: Xslt30TestSuiteDriverHE for Saxon 11 HE seems to consider higher-order functions as unavailablehttps://saxonica.plan.io/issues/5665?journal_id=216382022-08-27T23:24:08ZMichael Kaymike@saxonica.com
<ul></ul><p>I think this is dead code. The method <code>unavailableInXX</code> is used only when the -XX option to the test driver is used, and this option dates from when we had a version of the XX compiler that could be invoked from Java (with the Javascript parts, that is, the XPath parser) running under Nashorn. It also reflects the fact that at that time, SaxonJS didn't support higher-order functions.</p>
<p>We should probably get rid of this code now, because I doubt we will ever reinstate the ability to run the XX compiler from Java.</p>
<p>But it's true that the HE test driver isn't running HOF tests. This is because Xslt30TestDriverHE at line 1242 has</p>
<pre><code>needsEE.add("feature/higher_order_functions");
</code></pre>
<p>which is wrong and should be deleted.</p>
<p>I can confirm that if we change this, the tests run and (for those I've tested) they all pass.</p>
<p>QT3TestDriverHE has the same problem: lines 282-3 read</p>
<pre><code> } else if ("higherOrderFunctions".equals(value)) {
return (edition.equals("PE") || edition.equals("EE")) ^ inverse;
</code></pre>
<p>which needs to change to:</p>
<pre><code> } else if ("higherOrderFunctions".equals(value)) {
return !inverse;
</code></pre> Saxon - Support #5665: Xslt30TestSuiteDriverHE for Saxon 11 HE seems to consider higher-order functions as unavailablehttps://saxonica.plan.io/issues/5665?journal_id=216392022-08-28T06:12:59ZMichael Kaymike@saxonica.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>Michael Kay</i></li><li><strong>Fix Committed on Branch</strong> <i>11</i> added</li></ul><p>I have fixed the test drivers so the HE drivers now run the HOF tests (also, 1.0 backwards compatibility tests).</p>
<p>Under 11.x, this is giving 0 test failures for QT3, 5 test failures for XSLT 3.</p>
<pre><code> docbook-001 - reports "Can't make chunks with Saxonica's processor"
error-3175a - error not reported
mode-1506 - reports "SXST0068 Request for streaming ignored: this Saxon configuration does not support streaming"
sort-079 - incorrect handling of ignorable characters in collation
system-property-014b : expected result out="no", actual result out="4yes"
</code></pre> Saxon - Support #5665: Xslt30TestSuiteDriverHE for Saxon 11 HE seems to consider higher-order functions as unavailablehttps://saxonica.plan.io/issues/5665?journal_id=216402022-08-28T19:32:30ZMichael Kaymike@saxonica.com
<ul></ul><p>Fixed error-3175a with a change to the way the test driver handles the dynamic_evaluation dependency.</p>
<p>The same change also fixes system-property-014b.</p> Saxon - Support #5665: Xslt30TestSuiteDriverHE for Saxon 11 HE seems to consider higher-order functions as unavailablehttps://saxonica.plan.io/issues/5665?journal_id=216412022-08-28T19:37:53ZMichael Kaymike@saxonica.com
<ul></ul><p>Fixed mode-1506 by adding a dependency on streaming to the test metadata.</p> Saxon - Support #5665: Xslt30TestSuiteDriverHE for Saxon 11 HE seems to consider higher-order functions as unavailablehttps://saxonica.plan.io/issues/5665?journal_id=217722022-09-12T09:07:09ZMichael Kaymike@saxonica.com
<ul></ul><p>Current status is that we're getting three failures:</p>
<ul>
<li>docbook-001</li>
<li>sort-079</li>
<li>unparsed-text-2002</li>
</ul>
<p>I think the failure in unparsed-text-2002 is unrelated to this issue, and occurs because of recent changes to the W3C web site.</p> Saxon - Support #5665: Xslt30TestSuiteDriverHE for Saxon 11 HE seems to consider higher-order functions as unavailablehttps://saxonica.plan.io/issues/5665?journal_id=222262022-12-07T17:53:06ZMichael Kaymike@saxonica.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li></ul><p>I think we can now close this.</p>