W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2016

[Bug 29590] dependency cycle and indirect references

From: <bugzilla@jessica.w3.org>
Date: Tue, 26 Apr 2016 08:33:55 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29590-523-CpsaRDq7Mj@http.www.w3.org/Bugs/Public/>

--- Comment #4 from Michael Kay <mike@saxonica.com> ---
Interesting. Yes, I agree that it would be perfectly reasonable with
K2-InternalVariablesWithout-1a to go into infinite recursion rather than
detecting the error. 

Saxon is rejecting this one during a static check, which is a residue of XQuery
1.0 (which we still support, just about). Looking at the code, the static check
is actually too strong: it's capable of rejecting things that wouldn't fail at
run-time. Our static check appears to treat variable references and static
function calls as if they are always evaluated. Reading the rules, I don't
think that's conformant; the rules for conditional expressions and
switch/typeswitch don't allow you to raise an error as a consequence of
evaluating a branch of a conditional that isn't actually selected.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 26 April 2016 08:34:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:00 UTC