Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: 4ndre4 <626401fd-4bc7-4f8f-b641-563ae0f72920@626401fd-4bc7-4f8f-b641-563ae0f72920.invalid> Newsgroups: comp.lang.java.programmer Subject: Re: double == double Date: Sat, 15 Oct 2016 07:36:16 +0100 Organization: A noiseless patient Spider Lines: 12 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 15 Oct 2016 06:35:57 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="28b36f45a9be49094d07500bc598cea3"; logging-data="10126"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18SumCiay4gt4OAUgV2K9YM" User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 In-Reply-To: Cancel-Lock: sha1:+AfrcDBSEiAagQG8T4CusLhsQ0A= Xref: csiph.com comp.lang.java.programmer:35762 On 15/10/2016 03:37, Arne Vajhøj wrote: [...] > I think that the example seen as a whole actually say to avoid == on > double. Of course == on double should be avoided. As I said, it's a good rule to stick to. However, saying that comparing doubles via == *makes no sense* is formally wrong. -- 4ndre4