Re: [xsl] XPath that returns nothing

[Andrew Welch <andrew.j.welch@xxxxxxxxx>]

On 28 September 2011 10:01, David Carlisle <davidc@xxxxxxxxx> wrote:
> On 27/09/2011 09:42, Andrew Welch wrote:
>>
>> On 26 September 2011 22:17, Olivier Lefevre<lefevrol@xxxxxxxxx>  wrote:
>>>
>>> What is the best XPath expression that is guaranteed to return nothing?
>>> (best in the sense of simplest, always works and costs as little as
>>> possible to evaluate). I was hoping it'd be the empty string but that
>>> seems forbidden.
>>
>> Out of interest, why do you ask?
>>
>>
>>
>
> Usual reason for wanting this is as a default value for a parameter so you
> can go
>
> <xsl:param name="x" select="()"/.
> ...
>
> <xsl:value-of select="$x/a/b"/>

...so it's basically just making something explicit that is otherwise
implied?   I don't think I'd ever use it.

The part of the spec that talks about this:

------
If an optional parameter has no select attribute and has an empty
sequence constructor, and if there is no as attribute, then the
default value of the parameter is a zero length string.

[ERR XTDE0610] If an optional parameter has no select attribute and
has an empty sequence constructor, and if there is an as attribute,
then the default value of the parameter is an empty sequence. If the
empty sequence is not a valid instance of the required type defined in
the as attribute, then the parameter is treated as a required
parameter, which means that it is a non-recoverable dynamic error if
the caller supplies no value for the parameter.
------



--
Andrew Welch
http://andrewjwelch.com