Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: in praise of type checking Date: Thu, 06 Oct 2011 22:31:42 +0200 Lines: 18 Message-ID: <9f6hhqF717U1@mid.individual.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 1j1RCjgQ6JDRUdJK3Io9lwD/qhHZ1zDlgNUqEMkIkDflCabXs= Cancel-Lock: sha1:RRI8XGObukRPvgOGvDFcf7bgl08= User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:8606 On 06.10.2011 08:33, Roedy Green wrote: > I changed the result of a widely used method from boolean to int. The > neat thing was the compiler (actually the Intellij syntax checker) > made sure I fixed up every invocation of that method. It would not let > me forget even one. 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. Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/