From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Tolpin Message-Id: <200403051713.i25HDSt7060442@adat.davidashen.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] Inf isInf, NaN, isNaN In-Reply-To: <200403051447.i25Eljwo059910@adat.davidashen.net> Content-Type: text/plain; charset=KOI8-R Date: Fri, 5 Mar 2004 21:13:28 +0400 Topicbox-Message-UUID: 19dc4c88-eacd-11e9-9e20-41e7f4b1d025 > > 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?