Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: v_borchert@despammed.com (Volker Borchert) Newsgroups: comp.lang.java.programmer Subject: Re: Use of @Override when implementing interfaces Date: 7 Dec 2013 07:14:02 GMT Organization: Private site at Eddersheim, Germany Lines: 20 Distribution: world Message-ID: References: X-Trace: individual.net X8nEojHFwwYdjCG/RHrvIgKljxCJsrox9caYvoAE8qh8st+ixg Cancel-Lock: sha1:HpvQN9qqndvGK2zQgCM7gO3Tb+w= Xref: csiph.com comp.lang.java.programmer:26758 Fredrik Jonson wrote: > Is it commont practice to use @Override when implementing interface > methods? Assuming that the method has not been implemented by a > superclass. It helps reading the code of classes that have many methods, maybe some of them with similar sounding names, but only fsw implementing some not so well-known interface. For that reason, I'd even like @Override to allow a value indicating the class or interface where the overridden method lives. For now, I'm (ab-)using @see javadoc for this purpose, but that isn't part of the method's signature and therefore doesn't show up as prominently in IDEs' code completion suggestions etc. -- "I'm a doctor, not a mechanic." Dr Leonard McCoy "I'm a mechanic, not a doctor." Volker Borchert