W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2015

[Bug 29052] [xslt30ts] Test case error-0640o-2

From: <bugzilla@jessica.w3.org>
Date: Thu, 13 Aug 2015 15:01:45 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29052-523-MDduTpCw3t@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29052

--- Comment #7 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Aha, I see now where you are going: the circularity never comes into effect,
because the static error (variable not in scope) comes first. And because
setting a parameter's value and evaluating it is a dynamic-phase action, you'll
never get that far.

That is to say: there's still the issue that we do not require evaluation of an
expression when it is never used. But that's not true for static errors, so in
this case it ends up being wrong, because overriding the parameter comes too
late in the game.

How does that relate to:

<xsl:param name="foo" select="()" as="xs:string" />

which could also be a static error, but in this case we *do* allow the
parameter to be set, I believe we call this an "implicitly required parameter"?
Which begs the question: why allow/support this, but not the other?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 13 August 2015 15:01:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:55 UTC