xsl:analyze-string gives wrong results with bytecode enabled
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.
#1 Updated by O'Neil Delpratt over 4 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Applies to branch 9.8 added
- Fix Committed on Branch 9.6, 9.7, 9.8 added
Fix applied in the AnalyzeStringCompiler. The bytecode loop label was incorrectly put in a conditional
Bug fixed on the branches 9.6, 9.7 and 9.8.
Please register to edit this issue