[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
On 29/09/2011 03:24, Liam R E Quin wrote:
yes I do that a bit, but it still makes having two sockColor elements instead of one a fatal error and in our setup it's almost always better to complete the run and just log errors as they occur.
David
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. ________________________________________________________________________
Re: [xsl] XPath that returns nothing
Subject: Re: [xsl] XPath that returns nothing From: David Carlisle <davidc@xxxxxxxxx> Date: Thu, 29 Sep 2011 09:15:44 +0100 |
On 29/09/2011 03:24, Liam R E Quin wrote:
So use, as="element(sockColour)?" maybe?
You still get some additional sanity checking and maybe some performance benefits, with less strictness...
yes I do that a bit, but it still makes having two sockColor elements instead of one a fatal error and in our setup it's almost always better to complete the run and just log errors as they occur.
David
-- google plus: https:/profiles.google.com/d.p.carlisle
________________________________________________________________________ The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. ________________________________________________________________________
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XPath that returns nothin, Liam R E Quin | Thread | Re: [xsl] XPath that returns nothin, Andrew Welch |
Re: [xsl] XPath that returns nothin, Liam R E Quin | Date | Re: [xsl] XPath that returns nothin, Andrew Welch |
Month |