Path: csiph.com!1.us.feeder.erje.net!feeder.erje.net!2.eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!bcyclone05.am1.xlned.com!bcyclone05.am1.xlned.com!newsreader4.netcologne.de!news.netcologne.de!newsfeed.kamp.net!newsfeed.kamp.net!fu-berlin.de!uni-berlin.de!not-for-mail
From: Antoon Pardon <antoon.pardon@rece.vub.ac.be>
Newsgroups: comp.lang.python
Subject: Re: Floating point equality [was Re: What exactly is "exact" (was Clean Singleton Docstrings)]
Date: Wed, 20 Jul 2016 09:09:29 +0200
Lines: 35
Message-ID: <mailman.2.1468998615.22221.python-list@python.org>
References: <nlmpl5$9l4$1@dont-email.me> <nm6kbb$t6b$1@ger.gmane.org> <mailman.51.1468454075.21009.python-list@python.org> <7046c74e-e5ea-4dde-8847-8c556756a563@googlegroups.com> <5789B601.9000604@stoneleaf.us> <mailman.26.1468642801.2307.python-list@python.org> <9d2a0934-bf26-42a8-9bb2-e4e75b2d2ad3@googlegroups.com> <CAPTjJmq+VKdu7x_nzfP8fb=0EiAqWJO6_qKNsabQSnbBStyMsA@mail.gmail.com> <1468652038.1427719.667878897.460955C0@webmail.messagingengine.com> <mailman.28.1468652041.2307.python-list@python.org> <578a027c$0$1616$c3e8da3$5496439d@news.astraweb.com> <69d8d886-c18a-4c05-8bca-9a05afacd9a9@googlegroups.com> <578ca188$0$1505$c3e8da3$5496439d@news.astraweb.com> <877fcjcllf.fsf@elektro.pacujo.net> <CAPTjJmqYuhfR68g4EWWfj=GQSQMBmo3r3DRCej39xLtjPfR2ow@mail.gmail.com> <mailman.71.1468836914.2307.python-list@python.org> <578da1b5$0$1591$c3e8da3$5496439d@news.astraweb.com> <d0d6f677-35d0-4c79-a281-44317bbc11dd@googlegroups.com> <578f0f5c$0$11115$c3e8da3@news.astraweb.com> <578F23A9.7070105@rece.vub.ac.be>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.8.0
In-Reply-To: <578f0f5c$0$11115$c3e8da3@news.astraweb.com>
Precedence: list
Xref: csiph.com comp.lang.python:111661

Op 20-07-16 om 07:42 schreef Steven D'Aprano:
> Floating point maths is hard, thinking carefully about what you are doing and 
> whether it is appropriate to use == or a fuzzy almost-equal comparison, or if 
> equality is the right way at all.
>
> "But thinking is hard, can't you just tell me the answer?"
>
> No. But I can give some guidelines:
>
> Floating point arithmetic is deterministic, it doesn't just randomly mix in 
> error out of spite or malice. So in principle, you can always estimate the 
> rounding error from any calculation -- and sometimes there is none.

I would like to see a practical example of such an outcome.

> Arithmetic on integer-values (e.g. 1.0) is always exact, up to a limit of 
> either 2**53 or approximately 1e53, I forget which. (That's why most Javascript 
> programmers fail to notice that they don't have an integer type.) So long as 
> you're using operations that only produce integer values from integer arguments 
> (such as + - * // but not / ) then all calculations are exact. It is a waste of 
> time to do:
>
> x = 2.0
> y = x*1002.0
> is_equal(y, 2004.0, 1e-16)
>
> when you can just do y == 2004.0.

But why perforem integer arithmetics in floats, isn't that a waste of time too?
I really see no reason to use floats if you know all your results will be integers.

-- 
Antoon.