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

[Bug 28845] fn:format-number, formatting rules for exponential notation

From: <bugzilla@jessica.w3.org>
Date: Mon, 14 Sep 2015 16:50:05 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28845-523-j8D1eeulSU@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28845

--- Comment #12 from Michael Kay <mike@saxonica.com> ---
The fact that the percent and per-mille scaling can cause overflow (comment
#11) has been with us since XSLT 1.0 and is a purely theoretical problem
because no-one is likely to use percentages with such extreme values. There are
edge cases that we really don't need to legislate for.

I don't think that decimal overflow due to mantissa/exponent scaling is a very
serious problem either. I'm not sure our specs say so explicitly but I think
that in practice xs:decimal is usually implemented as floating point decimal.
The effect of format-number(), unless you write a really perverse picture, will
almost invariably change the exponent to be something fairly close to zero and
therefore very unlikely to blow any limits.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 14 September 2015 16:50:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 14 September 2015 16:50:09 UTC