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:36:24 -0700 Organization: Canadian Mind Products Lines: 24 Message-ID: <82lu87t4e47t1256r1vh7ich0esreter46@4ax.com> References: <9f6hhqF717U1@mid.individual.net> 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:8639 On Thu, 06 Oct 2011 22:31:42 +0200, Robert Klemme wrote, quoted or indirectly quoted someone who said : >I'm surprised you mention the compiler and syntax checker. In my >Eclipse changing the return type of a method is a refactoring which will >easily change all affected methods in code which is part of the project. > Lew's caveats apply of course. I changed the return type. That meant the caller now had to deal with 3 possible values instead of two. There is a no way a refactor can handle that. It is called Change Signature in IntelliJ. It is great for swapping parms, or changing a type, or adding a new parm. When you add a new parm, you still have to visit all the invocations to touch up if the default value does not apply. -- 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.