[9fans] Inf isInf, NaN, isNaN

[9fans] Inf isInf, NaN, isNaN

[David Tolpin]

Hi,

ape/math.h defines Inf, isInf, NaN, isNaN; but I cannot find them
in either ISO C standard, or my POSIX reference. Inf results in
a name conflict with an otherwise POSIX compliant source.

Instead, ISO/IEC 9989:1999 (The ISO C Standard) defines

isinf() and  isnan() macros, which are absent from the library.

David Tolpin

Re: [9fans] Inf isInf, NaN, isNaN

[Charles Forsyth]

>>Instead, ISO/IEC 9989:1999 (The ISO C Standard) defines
>>isinf() and  isnan() macros, which are absent from the library.

ape predates c9x, which (i suspect) added those--i don't remember
them from the earlier standard--but that's really just a cue
for doug gwyn to contradict me.  i'd check myself, but
for some reason, my c book is always where i am not.

Re: [9fans] Inf isInf, NaN, isNaN

[David Tolpin]

> >>Instead, ISO/IEC 9989:1999 (The ISO C Standard) defines
> >>isinf() and  isnan() macros, which are absent from the library.
>
> ape predates c9x, which (i suspect) added those--i don't remember
> them from the earlier standard--but that's really just a cue
> for doug gwyn to contradict me.  i'd check myself, but
> for some reason, my c book is always where i am not.
>

For me, the problem was not that isnan was not declared, but that
isNaN was. 

David

Re: [9fans] Inf isInf, NaN, isNaN

[David Tolpin]

> > ape predates c9x, which (i suspect) added those--i don't remember
> > them from the earlier standard--but that's really just a cue
> > for doug gwyn to contradict me.  i'd check myself, but
> > for some reason, my c book is always where i am not.
> >
>
> For me, the problem was not that isnan was not declared, but that
> isNaN was. 
>

That is, any chance Inf, isInf, NaN, isNaN can be locked out by
_POSIX_SOURCE or will it break something important enough?

Re: [9fans] Inf isInf, NaN, isNaN

[David Presotto]

[-- Attachment #1: Type: text/plain, Size: 18 bytes --]

For you, anything.

[-- Attachment #2: Type: message/rfc822, Size: 2554 bytes --]

From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Inf isInf, NaN, isNaN
Date: Fri, 5 Mar 2004 21:13:28 +0400 (AMT)
Message-ID: <200403051713.i25HDSt7060442@adat.davidashen.net>

> > ape predates c9x, which (i suspect) added those--i don't remember
> > them from the earlier standard--but that's really just a cue
> > for doug gwyn to contradict me.  i'd check myself, but
> > for some reason, my c book is always where i am not.
> >
>
> For me, the problem was not that isnan was not declared, but that
> isNaN was. 
>

That is, any chance Inf, isInf, NaN, isNaN can be locked out by
_POSIX_SOURCE or will it break something important enough?