Remove the test that ensures that when the string "nan(...)" is converted

to floating-point, the result is a quiet NaN.  The current implementation
may return a signaling NaN, and the vendor has no plans for changing this,
for reasons explained in the comment I added.
This commit is contained in:
das 2007-01-03 21:28:26 +00:00
parent e2797fe01c
commit 269e2dc492

View File

@ -190,7 +190,15 @@ main(int argc, char *argv[])
assert(f != f);
assert(d != d);
assert(ld != ld);
#if 0
/*
* POSIX says we should only generate quiet NaNs, but the gdtoa
* author convincingly argues that if you ask for a NaN format
* based on some implementation-defined string, you should get
* what you asked for, even if it's a signaling NaN.
*/
assert(fetestexcept(FE_INVALID) == 0);
#endif
printf("ok 2 - scanfloat\n");