News for hackers. Stuff that matters.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by Deestan on Monday May 02, 2011 @06:59PM (#2508255)
> You say "1.0/0.0 == +infinity" like it should be surprising, but it makes perfect intuitive sense to me.

But it isn't correct. 1/0 is undefined.

1/x approaches infinity as x approaches 0 from the positive side. 1/x approaches negative infinity as x approaches 0 from the negative side. If we were to define 1/0 it has to be both positive and negative infinity at the same time.

Re:Why floats suck - accurate galaxy-wide coordinates in 128... by bzbarsky on Monday May 02, 2011 @07:34PM (#2508357)
This is why IEEE floating point has -0.0, which represents sequences approaching 0 (underflow) from the negative side; 0.0 represents underflow from the positive side.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by palish on Monday May 02, 2011 @07:05PM (#2508267)
The goal for floats isn't to resolve equations. It's to perform arithmetic. (1.0 / 0.0) has to be handled somehow.

From a mathematical point of view, handling it as "+infinity" has a 50/50 chance of being "correct". As floating-point math is inherently an approximation, this is a reasonable tradeoff.

But from a pragmatic point of view, you don't care about the result of "x * foo" if x is +infinity or -infinity. The result isn't usable.

Re:Why floats suck - accurate galaxy-wide coordinates in 128... by andos on Monday May 02, 2011 @08:21PM (#2508470)
1.0/0.0 has to be handled somehow.

Yes, by raising an error [1]. Or whistling innocently and pretending it's not my code while leaving the room.

handling it as "+infinity" has a 50/50 chance of being "correct"

It has zero chance of being correct because infinity can never be the result of any arithmetic computation. Infinity is not a number. Infinity only appears as the result of evaluating limits, an operation which is not arithmetic.

[1] http://en.wikipedia.org/wiki/SIGFPE

Re:Why floats suck - accurate galaxy-wide coordinates in 128... by marshray on Monday May 02, 2011 @09:07PM (#2508588)
http://en.wikipedia.org/wiki/IEEE_754-1985

The spec allows the programmer to decide if the various degenerate cases in arithmetic will raise a signal, or result in a special value which propagates through the rest of the calcuations (INF, NaN, etc.).

Certainly there are times to prefer one over the other, but the facilities that were standardized back in the 80's are generally more than adequate for most uses.

Whether or not your platform C compiler lets you access these settings in a convenient and portable way is another question however...:-)

Re:Why floats suck - accurate galaxy-wide coordinates in 128... by andos on Monday May 02, 2011 @09:43PM (#2508663)
As long as everybody decides consciously whether to propagate garbage or raise flags, the world is safe.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by marshray on Tuesday May 03, 2011 @11:23AM (#2510283)
My policy is to prefer to signal or throw an exception. It's not something that can be accidentally ignored by an unconscious programmer.