Thankyou again for the explanation.  My SDL was not well-formed and the 
bad input was most likely do to sloppy loop control.  Since it happened 
at the end of a loop, it was just as easy to drop the offending 
calculation.

Thorsten Froehlich wrote:

> In article <vo2s7uc355p2c5e52bea9uva2ibjbqcndt@4ax.com> , W"odzimierz ABX 
> Skiba <abx### [at] babilonorg>  wrote:
> 
> 
>>AFAIK
>>
>>-1 != -1.#IND
>>
>>btw: I didn't found any place in 3.5 documentation where "#IND" is noted
>>and/or explained. It can confuse newbies.
>>
> 
> It is an artifact of the C library used.  Results may be different for
> different C libraries and thus this cannot be noted in the documentation.
> Further, checking for NANs and other invalid floating-point values was not
> part of the C standard until C99, so many compilers don't support those recent
> improvements yet.  For this reason, it remains the users' responsibility to
> only feed valid input into the various floating-point calculations in order to
> get valid output...
> 
>     Thorsten
> 
> ____________________________________________________
> Thorsten Froehlich, Duisburg, Germany
> e-mail: tho### [at] trfde
> 
> Visit POV-Ray on the web: http://mac.povray.org
>

Post a reply to this message