Actions
Bug #2117
closedByte code generation goes for boolean value instead of numeric
Start date:
2014-07-31
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:
Description
Reported by Gunther Rademacher:
When byte code generation is in effect, this XQuery
let $x := <x i="0"/>
return $x[1 + $x/@i]
is rejected with a message of
FORG0006: Effective boolean value is not defined for sequence starting with an atomic
value other than a boolean, number, or string
This problem first appears in 9.5.1.6
Updated by O'Neil Delpratt over 9 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Bug fixed and committed to subversion.
Given that the filter type is AnyAtomicType, statically we know that this is resolved to the numeric type double. In the bytecode class FilterExpressionCompiler we were taking into account only the integer types and disregarding other numeric types. This has been fixed for all numeric types.
Updated by O'Neil Delpratt over 9 years ago
- Status changed from Resolved to Closed
- Fixed in version set to 9.5.1.7
Bug fix applied in Saxon maintenance release 9.5.1.7
Please register to edit this issue
Actions