Re: [PATCH 1/4] Use nanf("") instead of nanf(NULL)
Joseph Myers <[email protected]>
| Newsgroups | gmane.comp.lib.newlib |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 27 Aug 2018, Craig Howland wrote: > Do we want to allow this recent GCC change to force a source change, when the > GCC change (added warning) is not a solid one? The C standard does not > require that the argument to nan() be non-null, although invoking general, The argument must, as per DR#477 (resolution integrated in C17), be a string. http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2257.htm#dr_477 -- Joseph S. Myers [email protected]