W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2011

[Bug 13028] [XQUF] Error in static typing rules for replace node Expr1 with Expr2

From: <bugzilla@jessica.w3.org>
Date: Thu, 23 Jun 2011 16:08:03 +0000
To: public-qt-comments@w3.org
Message-Id: <E1QZmRn-0004fi-95@jessica.w3.org>

--- Comment #4 from Michael Dyck <jmdyck@ibiblio.org> 2011-06-23 16:08:02 UTC ---
(In reply to comment #1)
> On a related note, the specification states that XUDY0027 is raised if the
> result of evaluating the target expression is an empty sequence.
> Why is this not a type error, and why do the static typing rules not prevent
> it?

Well, the static typing rules allow it because it's not a type error.

As to why it's not a type error... this question was raised in the WG about a
year ago:
It didn't get a definitive answer, but one person's recollection was that
making it a type error would have been unusable under static typing.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 23 June 2011 16:08:05 UTC

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