Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: in praise of type checking Date: Fri, 07 Oct 2011 12:43:19 -0700 Organization: Canadian Mind Products Lines: 24 Message-ID: References: <24031358.1064.1317908585192.JavaMail.geo-discussion-forums@prfp13> Reply-To: Roedy Green NNTP-Posting-Host: RCd/Ul4tyxGUBII8WGwa5g.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:8641 On Thu, 6 Oct 2011 06:43:04 -0700 (PDT), Lew wrote, quoted or indirectly quoted someone who said : > >It must not have been that widely used, then, if all the uses were in the o= >ne project. It was widely used within the project. It is internal code I use for generating references to bookstores/books/electronics at various online stores. Even if it were widely distributed, and even if it were a public method, type checking at least warns my clients I have changed the signature of a public method without warning them. They may want to shoot me, but at least they know precisely WHY they want to shoot me. -- Roedy Green Canadian Mind Products http://mindprod.com It should not be considered an error when the user starts something already started or stops something already stopped. This applies to browsers, services, editors... It is inexcusable to punish the user by requiring some elaborate sequence to atone, e.g. open the task editor, find and kill some processes.