Project

Profile

Help

Bug #17

closed

Incorrect optimization of xsl:value-of

Added by Anonymous over 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XSLT conformance
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Legacy ID:
sf-3480235
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

SourceForge user: mhkay

When Saxon is able to determine that the result of an xsl:value-of instruction will always be used as a string or untypedAtomic value (for example if it is used to construct the value of a variable where all uses of the variable are atomized), and when the select attribute is capable of returning an empty sequence, then the optimizer may generate code whose effect is that when the select expression is empty, the result of the xsl:value-of instruction is an empty sequence rather than a zero-length string. This may cause a subsequent type error (or other internal errors) when the expression is evaluated, since the client expression is not expecting xsl:value-of to return an empty sequence.

A patch (to module ValueOf) is being placed in Subversion.

Actions #1

Updated by Michael Kay over 12 years ago

  • Category changed from Internals to XSLT conformance
  • Assignee set to Michael Kay
Actions #2

Updated by Michael Kay about 12 years ago

  • Status changed from New to Resolved
  • Fixed in version set to 9.4.0.2
Actions #3

Updated by Michael Kay almost 12 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100

Please register to edit this issue

Also available in: Atom PDF