Subject:xpath processor bug? NaN = number(1) Author:Peter Smith Date:17 Feb 2003 06:44 PM
There seems to be a problem with a numeric comparison of NaN with the value 1. Please see the following. (Saxon and others didn't have this issue).
Xpath Processor Bug?: NaN = 1, including empty result
Value of $numeric_value:
Number value of $numeric_value:
Boolean value of $numeric_value:
NaN = 1? - $numeric_value = 1:
Forced to numeric - $numeric_value = number(1):
Forced to numeric - number($numeric_value) = 1:
Forced to boolean - $numeric_value = boolean(1):
Forced to boolean - boolean($numeric_value) = boolean(1):
BUILT-IN PROCESSOR RESULTS
Xpath Processor Bug?: NaN = 1, including empty result
Value of $numeric_value: NaN
Number value of $numeric_value: NaN
Boolean value of $numeric_value: false
NaN = 1? - $numeric_value = 1: true
Forced to numeric - $numeric_value = number(1): true
Forced to numeric - number($numeric_value) = 1: true
Forced to boolean - $numeric_value = boolean(1): false
Forced to boolean - boolean($numeric_value) = boolean(1): false
SAXON PROCESSOR RESULTS:
Xpath Processor Bug?: NaN = 1, including empty result
Value of $numeric_value: NaN
Number value of $numeric_value: NaN
Boolean value of $numeric_value: false
NaN = 1? - $numeric_value = 1: false
Forced to numeric - $numeric_value = number(1): false
Forced to numeric - number($numeric_value) = 1: false
Forced to boolean - $numeric_value = boolean(1): false
Forced to boolean - boolean($numeric_value) = boolean(1): false