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

[Bug 1896] New: Consistency between date/time overflow and numeric overflow

From: <bugzilla@wiggum.w3.org>
Date: Fri, 26 Aug 2005 17:26:48 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1E8hya-0007FJ-CR@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1896

           Summary: Consistency between date/time overflow and numeric
                    overflow
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators
        AssignedTo: ashok.malhotra@oracle.com
        ReportedBy: chamberl@almaden.ibm.com
         QAContact: public-qt-comments@w3.org


In bug 1489, we decided that casting from a string to a numeric type is treated 
as an overflow/underflow (e.g., FOAR0002, "Numeric operation 
overflow/underflow") if the resulting value is too big/small. But in casting 
from a string to a date/time/duration it is also possible that the value is too 
big/small to represent. The current F&O spec treats this as FORG0001, "Invalid 
value for cast/constructor". For consistency, should we change the error code 
for this condition to FODT0001 ("Overflow in date/time arithmetic") or FODT0002 
("Overflow in duration arithmetic")?
Received on Friday, 26 August 2005 17:26:54 UTC

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