On Sun, 14 Jan 2001 17:33:22 -0800, dan wrote:
>awsome, thanks!
>
>and sorry for posting it in the wrong place... chris young suggested it :-)
>this leads me to a question: Why does it not detect the NAN and drop out of
>the parse???

The question should be "why does the parser let me do things that return NaN
and not print a warning about it?"

I suspect that the reason it can't detect a NaN has something to do with 
portability across systems; there's no guarantee that every system uses 
IEEE floating point, so we can't check for NaN directly.

-- 
Ron Parker   http://www2.fwi.com/~parkerr/traces.html
My opinions.  Mine.  Not anyone else's.

Post a reply to this message