Saxonica Developer Community

2023-12-01

• 
  Michael Kay Saxon

  20:21 · Closed issue

  Bug #6271 (Resolved): In 4.0, reduced-arity coercion fails when target function has optional parameters

  See QT3 test case FunctionCall-417
  ```
  declare function local:f($x as xs:string, $y as xs:string, $z as xs:string := '1900-01-01') as xs:string {
  concat($x, '-', $y, ' on ', $z)
  };
  declare fun...
• 
  Michael Kay As suspected, a further fix was needed to handle references to system functions: change `SystemFunction.getFunctionItemType()` to return only as many argument types as appropriate for the value of `getArity()`.

  20:15 · Commented on issue
• 
  Michael Kay To get this example working I made the following changes:
  1. In UserFunction, add a method to get the function item type for a specific arity within the function's arity range. The current `getFunctionItemType()` method gets the maxim...

  18:49 · Edited issue
• 
  Michael Kay See QT3 test case FunctionCall-417
  ```
  declare function local:f($x as xs:string, $y as xs:string, $z as xs:string := '1900-01-01') as xs:string {
  concat($x, '-', $y, ' on ', $z)
  };
  declare fun...

  13:42 · Closed issue

2023-11-30

• 
  Michael Kay Saxon

  14:04 · Created issue

  Bug #6270 (New): In 4.0, downcasting coercion is not working for dynamic function calls

  Downcasting coercion (allowing 42 to be supplied where the required type is `xs:positiveInteger`) has been implemented for static function calls but not for dynamic function calls. Revealed by new test case fn-filter-406. The code in `Ty...

2023-11-29

• 
  Michael Kay Saxon

  13:27 · Closed issue

  Bug #6265 (Resolved): NPE in net.sf.saxon.functions.Contains

  The problem was initially reported here:
  https://listserv.brown.edu/cgi-bin/wa?A2=ind2311&L=TEI-L&P=24616
  It seems that one of our users who validates TEI XML documents using Schematron stumbled upon this NullPointerException:
  ```...
• 
  Michael Kay I've eliminated string() and substring-before|after(), my suspicions now fall on TraceExpression - which will only occur if the expression is compiled with tracing enabled. I suspect Oxygen is inserting trace calls into the expression at...

  11:31 · Commented on issue
• 
  Michael Kay Well, there are only 12 implementations of `elaborateForString()` so I could start by checking them all...
  One possible culprit is String_1.elaborateForString(), which evaluates the `string()` function.
  SubstringAfter and SubstringBefo...

  10:56 · Commented on issue
• 
  Michael Kay I'm afraid it's going to be difficult to do much with this without a repro.
  There's clearly a call on `fn:contains(x, y)`, and the code for evaluating y has returned null to represent an empty sequence when it was asked to return "" (...

  10:55 · Commented on issue

2023-11-28

• 
  Michael Kay Saxon

  13:10 · Commented on issue

  Moving the code that sets eagerEvaluation from `TryCatch.optimize()` to `TryCatch.typeCheck()` solves the problem for the opt:0 case, but not for the `opt:lvmt` case, as one would expect from the above analysis. Bug #6263: Test case try-031 fails under Saxon-HE (try/catch with lazy evaluation)

  The XSLT 3.0 test case try-031 is failing under Saxon-HE. The essence of the failure is that in the construct
  ```
  <xsl:variable name="p" select="...."/>
  <xsl:try>
  <xsl:value-of select="$p"/>
  <xsl:catch>
  <caught/>
  ...