W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2010

[Bug 4551] K-NormalizeUnicodeFunc-13

From: <bugzilla@jessica.w3.org>
Date: Tue, 30 Nov 2010 01:24:26 +0000
To: public-qt-comments@w3.org
Message-Id: <E1PNExG-0001XX-Ub@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4551

Josh Spiegel <josh.spiegel@oracle.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |REOPENED
         Resolution|FIXED                       |

--- Comment #12 from Josh Spiegel <josh.spiegel@oracle.com> 2010-11-30 01:24:24 UTC ---
I think this fix is incomplete.  

I can see that XPST0005 was added for K-NumericAdd-34 and K-NumericAdd-35 but
the tests themselves seem unchanged.  I don't think adding XPST0005 makes sense
unless you also change the tests as described in comment #8.  

I don't see any changes for K-ValCompTypeChecking-39 or
K-ValCompTypeChecking-41 even though comment #10 indicates they have changed.

If K-NormalizeUnicodeFunc-13 accepts XPTY0004 as a valid result, it seems odd
to me if the tests in comment #7 do not accept XPTY0004 as well. i.e. isn't
Tim's analysis in comment #3 valid for the comment #7 tests as well -
"(integer, none) isn't a subtype of integer"? I expected the fix to be adding
XPTY0004 as a valid result for each of the comment #7 tests (not XPST0005).

-- 
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 Tuesday, 30 November 2010 01:24:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:08 GMT