"Bald Eagle" <cre### [at] netscapenet> wrote:
> Following up,
>
> It looks like this is a general "undefined" state for Windows.
> My money is divide by zero error in normalizing the vector to unit length.
>
I agree.


> https://www.mathworks.com/matlabcentral/answers/31571-1-io-error-on-xpc
>
>
https://stackoverflow.com/questions/35997187/what-leads-to-the-floating-point-exception-1-io
>
> https://www.sierrachart.com/SupportBoard.php?ThreadID=14054
>
>
https://unmethours.com/question/24410/-1io-error-value-when-running-battery-storage-in-e/
>
> I'd simply check vlength (Vector) before proceeding, and exit early if a
> zero-length vector is the input.
>
Yea! That's what I did before I posted here. I just never seen -1.#IO before.
And the spline behavior through me. I thought I'd at less get an error saying
don't do that.

> (Using those values in a #if statement should still not crash POV-Ray)
>
Today I tried again to make it crash. And of course it didn't. All I get is :
Parse Error: Expected 'numeric expression', undeclared identifier 'IO' found
instead
Your second link here may have the answer. It said :

"That -1.#IO propogates to all of the other subroutines so eventually I have
thousands of variables with this exception before it blows up"

I did have my first test at the end of the file I was working on.

Have Fun!

Post a reply to this message