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

[Bug 29679] [XQ3Ts] same-key-008

From: <bugzilla@jessica.w3.org>
Date: Mon, 18 Jul 2016 16:37:58 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29679-523-szS3BwnPsa@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29679

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #5 from Michael Kay <mike@saxonica.com> ---
Yes, I think you are correct.

When you take an xs:float value F, for example the xs:float approximation to
the value of 1/3, and cast to a decimal, you don't necessarily get a decimal
that is mathematically equal to F. That is to say

op:same-key(xs:decimal(F), F)

is not necessarily true.

I think what happened is that in the email thread we decided to retain the
status quo in the spec, but we never decided that the test case was therefore
valid.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 18 July 2016 16:38:10 UTC

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