Actions
Bug #2688
closedxsl:analyze-string gives wrong results with bytecode enabled
Status:
Closed
Priority:
Normal
Assignee:
Category:
Byte code generation
Sprint/Milestone:
Start date:
2016-03-25
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.6, 9.7, trunk
Fix Committed on Branch:
9.6, 9.7, trunk
Description
Reported by David Rudel on saxon-help list.
With bytecode enabled, a call on xsl:analyze-string using the regex separator "\r\n", with an xsl:non-matching-substring child and no xsl:matching-substring child, appears to execute the xsl:non-matching-substring child twice for each line in the input, once with the actual line content as the value of ".", and once with the single character "\r" (x0D).
Reported on 9.6, but reproduced on 9.7.
Please register to edit this issue
Actions