Bug #2688
closedxsl:analyze-string gives wrong results with bytecode enabled
100%
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.
Updated by O'Neil Delpratt over 8 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.
Updated by O'Neil Delpratt over 8 years ago
- Fixed in Maintenance Release 9.7.0.5 added
Bug fix applied in the 9.7.0.5 maintenance release. Leaving this bug open until fix is applied in the 9.6 maintenance release.
Updated by O'Neil Delpratt over 8 years ago
- Status changed from Resolved to Closed
- Fixed in Maintenance Release 9.6.0.9 added
- Fixed in Maintenance Release deleted (
9.7.0.5)
Bug fix applied in the Saxon 9.6.0.9 maintenance release.
Updated by O'Neil Delpratt over 8 years ago
- Fixed in Maintenance Release 9.7.0.5 added
Updated by O'Neil Delpratt over 7 years ago
- Applies to branch trunk added
- Applies to branch deleted (
9.8)
Updated by O'Neil Delpratt over 7 years ago
- Fix Committed on Branch trunk added
- Fix Committed on Branch deleted (
9.8)
Please register to edit this issue