Subject: Re: [xsl] The operator '!=' returns false when one operand doesn't exist From: Michael Fuller <msf@xxxxxxxxxxxxxxx> Date: Thu, 8 Aug 2002 09:13:43 +1000 |
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>) 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>) !! :-) Enjoy. Michael XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] The operator '!=' returns, Michael Kay | Thread | Re: [xsl] The operator '!=' returns, G. Ken Holman |
RE: [xsl] Catching Parser/Transform, Michael Kay | Date | Re: [xsl] attribute closest match, Alex Sharpe |
Month |