[Webkit-unassigned] [Bug 25645] SVG - numeric overflow for very large elements

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=25645





--- Comment #25 from W. James MacLean <wjmaclean at chromium.org>  2010-05-06 10:21:37 PST ---
(In reply to comment #24)
> 
> The same issue can exist with numbers at the extreme range of what double can
> represent, and in the case of double using a larger floating point number is
> not practical. One way to fix this is to build digit by digit in the opposite
> direction after counting digits. This is what the constant
> mantissaOverflowLowerBound and parseIntOverflow in JSGlobalObjectFunctions.h
> are written to deal with. We might want to take a similar approach for float.

I agree that a right-to-left parsing of the number is appropriate. It's also
more effort, so the questions in my mind are:

1) Should we implement a double-based short-term fix before doing a full-blown
parser (based on the notion that we will do the full-blown parser, but it will
take longer)? 

and

2) In the full blown parser, what rules are appropriate for those numbers that
cannot be represented (too large, too much precision, etc.)?

I would think any compiler has standard code to solve this type of problem.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.