- From: <bugzilla@jessica.w3.org>
- Date: Mon, 05 Oct 2015 11:40:31 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=4378
--- Comment #25 from Josh Spiegel <josh.spiegel@oracle.com> ---
I agree with Tim that using the function body context item should be a static
error.
Mike, I don't understand why allowing a static error in this case would be a
"fairly disruptive change". For example, you said "Saxon in effect rewrites
"." within a function body as fn:error("XPDY0002")". It isn't clear to me why
you can't simply raise a static error at this point instead.
But yes, whether it is a static error or a type error that can be raised
statically, implementations should not be forced to make any incompatible
changes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 5 October 2015 11:40:45 UTC