Subject: [xsl] overriding xpath functions From: Jakub Malý <jakub@xxxxxxx> Date: Fri, 9 Mar 2012 09:26:13 +0100 |
Hello, maybe dumb question - what happens when a processor encounters an expression using the eq operator (and the other related operators)? Since eq is sort of overloaded and calls different functions according to the type of the operands (op:numeric-equal, fn:compare etc). And especially when the operands are empty sequences - like in () eq ()? The result is an empty sequence*, but what steps lead to it? Follow-up question - is it possible to override the built-in xpath functions in XSLT or XQuery? * is it written somewhere in the specs, that eq returns empty sequence when some of the operands is an empty sequence? I looked, but did not find it.. Thanks, Jakub.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Alternate header for mult, Philip Vallone | Thread | Re: [xsl] overriding xpath function, Michael Kay |
Re: [xsl] double spaces how do i ke, Michael Schäfer | Date | Re: [xsl] overriding xpath function, Michael Kay |
Month |