Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: @Override Date: Tue, 24 Jul 2012 09:46:36 +0200 Lines: 22 Message-ID: References: <75036e8b-8b5f-4ea4-aef7-c063249f5707@googlegroups.com> <9da89e66-d7df-47e1-84d4-2dddea7d744f@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net qKzdjqprOw1eOxatUOkpyAV+e/JvXdWmUPQRk7WWeVB5wlQaHG9GaBkhiMbmmYmd0= Cancel-Lock: sha1:6i8WjsPM+fP8/eaV4A0xEq6GW4A= User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 In-Reply-To: <9da89e66-d7df-47e1-84d4-2dddea7d744f@googlegroups.com> Xref: csiph.com comp.lang.java.programmer:16298 On 23.07.2012 22:59, Lew wrote: > Add the third benefit that I mentioned upthread. Aren't they enough now? Are variant of this is where the super class or interface is in a library and a later version removed the method. You'll immediately notice when replacing the lib with the newer version. This is a good thing (being noticed - not removing something from a public API) and you are immediately aware that your method won't be invoked the same way as it used to be. Granted this should be a rare situation but - for example - if the library method had been deprecated and you somehow missed adjusting your code to the imminent removal the compiler will force it on you once it is gone. Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/