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

[Bug 29199] [QT3TS] cbcl-cast-date-004, cbcl-cast-dateTime-004

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Nov 2015 15:57:01 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29199-523-o7yoeC3IuH@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29199

Abel Braaksma <abel.braaksma@xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |abel.braaksma@xs4all.nl

--- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
> if the value is too large or too small to be represented by the implementation, 
> a dynamic error [err:FODT0001] is raised.

I have had a similar discussion a while back (can't remember the bug id), but I
believe this was *only* for cases were facets are out of bounds, *after*
parsing.

The question is, is this date format invalid ("QQ") or is it overflowing
("18446744073709551616"). I'd argue that any type first needs to be parsed
before it gets converted into an internal data representation, in which case
this would *not* be an overflow case, but an invalid date case.

Note, from a parsing perspective, the XSD facet for year allows
"18446744073709551616". So, during parsing and facet validation, this part is
valid, only after that the overflow *may* kick in, but we never get that far.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 November 2015 15:57:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 November 2015 15:57:04 UTC