-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 3/29/2008 3:29 PM:
| Therefore, I'm asking for opinions - should I apply this patch as is, to
| at least guarantee 'inf' and 'nan' parsing on all platforms, even though
| it can cause regressions on the accuracy of the parse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ftell failed to compile on mingw due to missing EOVERFLOW (I hadn't
noticed this, since M4 was using only ftello). In the process of fixing
this, I also beefed up the ftell/o tests to check behavior after ungetc.
Mingw ftell is weird when used on tex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow - I had no idea that strtod implementations were so buggy. Of all the
systems I tried, I did not find a single one that was fully C99 compliant.
glibc 2.3.6 has several bugs, such as when parsing "-0x" or "nan()".
glibc 2.4 has improvements, bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 3/29/2008 5:59 AM:
| At this point, waiting for a resolution by the Austin Group (Geoff Clare's
| mail is an important opinion, but not yet a decision), I prefer to not
change
| the code, but just disable the test.
Thanks
Eric Blake wrote:
> Cygwin 1.5.25-11 implements 1a+2a, and does not require an fflush
> replacement by any of the current tests in fflush.m4. Therefore, cygwin
> fails test-fflush2.c
> ...
> At this point, I would even be happy with a solution that enforces 1a ...
Oops, you are right. My previous
