XX Compiler failure with static parameters whose type has an occurrence indicator
#1 Updated by John Lumley 3 months ago
This is a puzzle... certainly there are cases of the XX compiler compiling the testdriver successfully - and that certainly contains static parameters used for conditional compilation.
Sent from my iPad
On 28 Jun 2020, at 15:18, Saxonica Developer Community email@example.com wrote:
#2 Updated by John Lumley 3 months ago
- Status changed from New to In Progress
- Applies to JS Branch Trunk added
A minimal reproduction of the problem occurs with:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="#all" version="3.0"> <xsl:param name="xslt-uri" static="yes" as="xs:string?" select="'group-sales-sum-product.xsl'"/> </xsl:stylesheet>
which fails in the static phase with
as="xs:string?" but succeeds with
#3 Updated by John Lumley 3 months ago
The strategy for handling type declarations on such static variables has been to wrap the expression in a casting function, for example:
<xsl:param name="length" as="xs:decimal" select="12+34"/>
involves an evaluation of the XPath expression '
Unfortunately this has never been tried with a cardinality indicator, so the compiler has been trying to parse
which on encountering the
? operator, assumes a lookup and takes the left hand operator to be a
child::xs:string term. In this case there is no context focus and hence the error.
#5 Updated by Debbie Lockett 3 days ago
- Assignee changed from John Lumley to Debbie Lockett
- Applies to JS Branch deleted (
- Fix Committed on JS Branch 2.0 added
The code patch was committed to the saxon-js-enterprise git repo on 2020-06-29.
A test should be added (XSLT3 probably?), and then the bug can be closed.
Please register to edit this issue