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: Use of @Override when implementing interfaces Date: Fri, 06 Dec 2013 08:18:14 -0800 Organization: A noiseless patient Spider Lines: 27 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 6 Dec 2013 16:18:18 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="9358cda03e1e0dfd3c4b757daa608707"; logging-data="20150"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/FOlJDo7KwlTg2ILMifRRVCxvRE9QvvgE=" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 In-Reply-To: Cancel-Lock: sha1:E1dal0TXjCDFmSjMdVM28q0BvyA= Xref: csiph.com comp.lang.java.programmer:26752 On 12/6/2013 7:36 AM, Leif Roar Moldskred wrote: > > In my experience, it's not _uncommon_, but I wouldn't say it's common > either. > > It can be useful to have @Override in place on interface methods when > you're refactoring or otherwise modifying the interface being > implemented, in particular it helps to prevent dead code when you > delete methods from an interface. > Also, if the interface were less well known that Runnable, it would be helpful for a maintainer to see which methods were overridden. public class Fubar implements ArgleBargle { public void doThing() {} @Override public void otherThing() {} } This makes one suspect that "doThing"is not part of the ArgleBargle interface, but something new added in Fubar.