Subject: Re: [xsl] what could select="self:node()[false()] be for? From: David Carlisle <davidc@xxxxxxxxx> Date: Fri, 18 Oct 2002 15:01:17 +0100 |
<xsl:param name="data" select="self::node()[false()]"/> could be doing; is supposed to do; does it make any sense? it is declaring the parameter and giving it a default value of an empty node set. Yes it does make sense, I usually usse "/.." for that but the above would do. If you expect a param to be passed in as a node set then if you leave thedefault being <xsl:param name="data" /> it will be an empty string and things like select="$param/a/b" would be a type error. However if you make the default an empty node set then these expressions are legal but select nothing, which may be what is required. David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] what could select="self:n, Joerg Heinicke | Thread | RE: [xsl] what could select="self:n, Michael Kay |
Re: [xsl] Alternating Odd and Even , Kuhns Matt | Date | Re: Functional Language wasRE: [xsl, Jeff Kenton |
Month |