Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: markspace Newsgroups: comp.lang.java.programmer Subject: Re: The Assignment Principle Date: Mon, 27 Jan 2014 13:33:25 -0800 Organization: A noiseless patient Spider Lines: 14 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Mon, 27 Jan 2014 21:33:27 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="9358cda03e1e0dfd3c4b757daa608707"; logging-data="2702"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/poChrgX0Pspc/AanURJaEf+ohquYnxpk=" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: Cancel-Lock: sha1:LL2iIAuH5e3TSrM+nxUzWVsDrOk= Xref: csiph.com comp.lang.java.programmer:27410 On 1/27/2014 9:50 AM, Robert Klemme wrote: > > That's why I would disagree calling Math.random() an exception. So > basically the original quoted principle can only reasonably apply to > values (object references and primitive type values). And there NaN is > really an exception. Too many exceptions mean that the rule is wrong, imo. I'm going to stick with "non-functional languages have their own set of rules" and not try to shoe-horn Java into a functional mindset and end up with a bunch of exceptions to each and every rule of functional programming.