On Wed, 10 Jul 2013, Garrett Wollman wrote:
< said:
I think isnan(double) and isinf(double) in math.h should only be
visible if (_BSD_VISIBLE || _XSI_VISIBLE) && __ISO_C_VISIBLE < 1999.
For C99 and higher there should only be the isnan/isinf macros.
I believe you are correct. POSIX.1-2008 (
On Thu, 11 Jul 2013, David Chisnall wrote:
You're joining in this discussion starting in the middle, so you probably
missed the earlier explanation.
I was mainly addressing a C99 point. I know little about C++ or C11.
On 11 Jul 2013, at 05:21, Bruce Evans wrote:
I don't s
On Thu, 11 Jul 2013, Tijl Coosemans wrote:
On 2013-07-11 06:21, Bruce Evans wrote:
On Wed, 10 Jul 2013, Garrett Wollman wrote:
< said:
I think isnan(double) and isinf(double) in math.h should only be
visible if (_BSD_VISIBLE || _XSI_VISIBLE) && __ISO_C_VISIBLE < 1999.
For
On Thu, 11 Jul 2013, David Chisnall wrote:
On 11 Jul 2013, at 13:11, Bruce Evans wrote:
is also not required to be conforming C code, let alone C++ code,
so there is only a practical requirement that it works when included
in the C++ implementation.
Working with the C++ implementation is
On Thu, 11 Jul 2013, David Chisnall wrote:
On 11 Jul 2013, at 13:11, Bruce Evans wrote:
The error message for the __builtin_isnan() version is slightly better up
to where it says more.
The less-unportable macro can do more classification and detect problems
at compile time using __typeof
On Sat, 31 Jan 2015, Peter Jeremy wrote:
To resurrect an old thread...
On 2014-Mar-25 17:22:05 -0700, Steve Kargl
wrote:
It appears that clang developers have chosen the naive
complex division algorithm, and it does not matter whether
one turns CX_LIMITED_RANGE on or off. This means that
if
On Sat, 28 Mar 2015, Mark Millard wrote:
With reference to Dimitry Andric's Thu Mar 26 14:41:43 UTC 2015 note ...
[... gcc's "fixing" of headers]
Indeed. See also this recent discussion on -current:
https://lists.freebsd.org/pipermail/freebsd-current/2015-March/055111.html
where a "fixe
