This is the mail archive of the xsl-list@mulberrytech.com mailing list .
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
A nuance regarding comparisons should be addressed in this response: At 2002-08-08 09:13 +1000, Michael Fuller wrote:
Jerome Louvel wrote: > We have an issue with the XPath '!=' operator [...] As others have observed, this is the defined behaviour for nodesets. For example, given the nodesets NS1: {<a>-1</a>, <b>0</b>, <c>1</c>} and NS2: {<X>0</X>} this means that all of the following relationships hold: NS1 = NS2 (the string value of the node <X>0</X> in the second set is equal to the string value of the node <b>0</b>) NS1 != NS2 (the string value of the node <X>0</X> in the second set is not equal to the string value of the node <a>-1</a>)
Fine above.
Note that in any expression with "<" and ">", it is the number value conversion of the string value of the node that is compared, and not the string value as documented above.NS1 < NS2 (the string value of the node <X>0</X> in the second set is > the string value of the node <a>-1</a>) NS1 > NS2 (the string value of the node <X>0</X> in the second set is < the string value of the node <c>1</c>) NS1 >= NS2 (the string value of the node <X>0</X> in the second set is >= the string value of the node <b>0</b>) NS1 <= NS2 (the string value of the node <X>0</X> in the second set is >= the string value of the node <b>1</b>)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |