https://bugs.winehq.org/show_bug.cgi?id=48160
Erich E. Hoover erich.e.hoover@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #65961|0 |1 is obsolete| |
--- Comment #9 from Erich E. Hoover erich.e.hoover@gmail.com --- Created attachment 66005 --> https://bugs.winehq.org/attachment.cgi?id=66005 implement strtod without using 'long double'
(In reply to Alexandre Julliard from comment #8)
I don't think we want to return exactly 0 if Windows doesn't. But it doesn't really matter how we achieve that.
I looked into this a bit more and that may not actually be the case. It looks like what happens in this case is that Windows switches over to denormal values (1e-309 is represented as 0.1e-308). So, returning any old value under DBL_MIN is likely to break something. I have attached an updated patch that takes this into account (and updates the tests to demonstrate this behavior). Is this something that you would be receptive to having submitted during code freeze?