Bug in floating-point addition: is anyone else seeing this?

[Chris Mellon]

On Wed, May 21, 2008 at 3:56 PM, Dave Parker
<daveparker at flamingthunder.com> wrote:
> On May 21, 2:44 pm, "Jerry Hill" <malaclyp... at gmail.com> wrote:
>
>> My understand is no, not if you're using IEEE floating point.
>
> Yes, that would explain it.  I assumed that Python automatically
> switched from hardware floating point to multi-precision floating
> point so that the user is guaranteed to always get correctly rounded
> results for +, -, *, and /, like Flaming Thunder gives.  Correct
> rounding and accurate results are fairly crucial to mathematical and
> scientific programming, in my opinion.
> --

If you're going to use every post and question about Python as an
opportunity to pimp your own pet language you're going irritate even
more people than you have already.