Interval arithmetic is far from trivial. 1/(1/x+1/y) is not the same as xy/(x+y). It breaks things more than normal floating point math does.
This unfortunately breaks with something like [+1, +1] / [-1, +1] which yields (-∞, -1] and [+1, +∞), the result falls into two separate intervals. Now you can either turn this into (-∞, +∞) or use sets of intervals instead of single intervals. The first option gives pretty useless results, the second one can become really slow and consume a lot of memory. You can make this work, but you have to be really careful what you are calculating and how you are doing it.
Re:0.30000000000000004
by daurnimator on Sunday April 02, 2017 @08:41PM
(#14019892)
> The first option gives pretty useless results
Does it though? Wouldn't a result of `(-∞, +∞)` be a solid indication to go and reduce the range of your input parameters?
Interval arithmetic can be used, although that requires double the storage for all the intermediate results, and extra work.
For example, .1 can be represented by x=[x0, x1], where x0 and x1 are floating point values bracketing .1, and similarly .2 can be represented by y=[y0, y1].
Then z=[z0, z1] can be computed by "z=x+y", where the interval z respects the sum of both intervals x and y.
When printing, you can determine the smallest representation within the interval z.
I'm not sure if it's worth all the trouble though :)