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

[Bug 29419] [XP31] edge case with negative integer literals (UnaryExpr) and limits for -9223372036854775808, which cannot be parsed

From: <bugzilla@jessica.w3.org>
Date: Wed, 15 Jun 2016 15:52:02 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29419-523-bW5FPwkmpE@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29419

--- Comment #18 from Jonathan Robie <jonathan.robie@gmail.com> ---
Minutes from the meeting are here. We kept the 18 digits recommendation - and
it is in a NOTE, so it is not normative. I neglected to add the first
paragraph, I will do so now.

https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0031.html

CMSMcQ: Here is a version of the note in comment 8 without RECOMMENDED and
SHOULD:

     The effect of the above rule is that in the case of an integer or
     decimal literal, a dynamic error FOAR0002 will generally be raised if
     the literal is outside the range of values supported by the
     implementation (other options are available: see [F+O section 4.2] for
     details.)

     The XSD specification allows implementations to impose a limit (which
     must not be less than 18 digits) on the size of integer and decimal
     values. The full range of values of built-in subtypes of xs:integer,
     such as xs:long and xs:unsignedLong, can be supported only if the
     limit is 20 digits or higher. Negative numbers such as the minimum
     value of xs:long (-9223372036854775808) are technically unary
     expressions rather than literals, but implementations may prefer to
     ensure that they are expressible.

DECISION: add CMSMcQ's Note to the XPath spec.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 15 June 2016 15:52:06 UTC

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