Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Re: Determining whether no single instance of a specific

From: John Snelson <john.snelson@------.--->
To: xsl-list@-----.------------.---
Date: 6/5/2009 4:02:00 PM
Michael Ludwig wrote:
> Michael Kay schrieb:
>> In XSLT 1.0, applying count() to anything other than a node-set is an
>> error (one of the very few dynamic errors defined in XPath 1.0).
> 
> Is a "dynamic error" just another word for "runtime error"?

Mostly - but if the implementation can prove that a dynamic error is 
always raised during evaluation, it is free to raise it at compile time.

> Is a "static error" then the same as a "compile-time error"?

A static error is certainly raised during compilation - but it's not the 
only type of error that can be.

There's also type errors, which can be raised at compile-time or runtime 
regardless of whether you can prove they will always be raised during 
execution.

John

-- 
John Snelson, Oracle Corporation            http://snelson.org.uk/john
Berkeley DB XML:            http://oracle.com/database/berkeley-db/xml
XQilla:                                  http://xqilla.sourceforge.net

--~------------------------------------------------------------------
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@l...>
--~--



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent