Re: [xsl] XPath that returns nothing

On Wed, 2011-09-28 at 12:07 +0100, David Carlisle wrote:
[...]
>  if you have a function that expects a single 
> element and you go
> xsl:param name="x" as="element()"
> then if one of the input documents is bad the error percolates up to the 
> top level and not only that document fails to produce but the entire run 
> is aborted.

So use, as="element(sockColour)?" maybe?

You still get some additional sanity checking and maybe some performance
benefits, with less strictness...

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/

Current Thread
Re: [xsl] XPath that returns nothing, (continued) Andrew Welch - 28 Sep 2011 10:18:23 -0000 David Carlisle - 28 Sep 2011 10:25:29 -0000 Andrew Welch - 28 Sep 2011 10:34:14 -0000 David Carlisle - 28 Sep 2011 11:07:38 -0000 Liam R E Quin - 29 Sep 2011 02:25:14 -0000 <= David Carlisle - 29 Sep 2011 08:16:00 -0000 Andrew Welch - 29 Sep 2011 09:06:52 -0000 Michael Kay - 29 Sep 2011 09:27:43 -0000 Andrew Welch - 29 Sep 2011 10:14:40 -0000

Current Thread

Re: [xsl] XPath that returns nothing, (continued)

<- Previous	Index	Next ->
Re: [xsl] XPath that returns nothin, David Carlisle	Thread	Re: [xsl] XPath that returns nothin, David Carlisle
Re: [xsl] [ANN] New XSL-FO 2.0 Work, Tony Graham	Date	Re: [xsl] XPath that returns nothin, David Carlisle
	Month

<-prev [Thread] next->	<-prev [Date] next->
Month Index \| List Home