On 4/19/2014 7:01 PM, Michael Kay wrote:
Is it then a logical conclusion to try to avoid (never use) the
xs:error type in XPath?
I'm not aware of any use cases where it's useful, but someone might well
discover one. It's rather like the type empty-sequence(); it's logically
necessary for completeness, but that doesn't mean it's useful in practice.
Functions that are declared as returning empty-sequence() are most
likely operating via side-effect; I would think this would be a pretty
good indicator to an optimizer that it is not safe to remove calls to
them. I understand that XQuery is functional and likes to pretend there
are no side effects, but in practice, there are, no? We are defining
file operations, and any time we touch external systems there is the
potential for side effects.
-Mike
--~------------------------------------------------------------------
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(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--