Subject: RE: [xsl] Selecting the first node set From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Tue, 15 Aug 2006 10:31:59 -0400 |
> One has to be willing to think with the > literal-mindedness of a machine to tell the difference > between /descendant-or-self::node()/child::Value[1] and > (/descendant-or-self::node()/child::Value)[1], and that can > take a bit of practice.
Yes. I'm not sure why people struggle with this though. It seems intuitive enough that
x | y[1]
doesn't mean the same as
(x | y)[1]
so why is the "/" perceived so differently from the "|"? Is it that people are somehow aware that it's a higher-order operator and therefore imagine it doesn't obey normal precedence rules? Or is it the overloading of [], which in its other role as a boolean filter is associative with "/"?
Cheers, Wendell
Michael Kay http://www.saxonica.com/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Selecting the first node , Michael Kay | Thread | Re: [xsl] Selecting the first node , Florent Georges |
[xsl] Only first rows (after the so, Stinissen, Dennis | Date | Re: [xsl] Selecting the first node , Wendell Piez |
Month |