That reminds me, i have a situation where i have
count(ancestor::Menu[1]|$snode)=1
i then changed to
count(parent::Menu|$snode)=1
and it stop working. Isn't ancestor::Menu[1] and parent::Menu
equivalent since the ancestor axis is going backward?
Likewise, (ancestor::Menu)[1] should give the first ancestor in
document order, that is to say the anciest ancestor of the context
node.
Am i not correct? If so why my xsl stop working (or better, it works
in a way i don't expect) after that change?
On Sat, 19 Feb 2005 10:40:29 GMT, David Carlisle
<davidc(_at_)nag(_dot_)co(_dot_)uk> wrote:
Joris
1)The union operater '|' works only for node-sets, not boolean value. Use
'or' here.
actually | works here as well, you have two node sets so either you
coerce them each to booleanand use or or you take their union and then
coerce to a boolean, it comes to the same thing.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--