On Wed, 27 Jun 2012 18:16:03 -0300, Ulrich Stärk <[email protected]> wrote:
I personally don't like the use of @Override on mere method implementations. The naming (and also the JavaDocs) imply that methods supposed to override superclass methods are to be annotated with it. Overriding is replacing an /existing/ implementation in a superclass or parent class with a different one. With interface implementations or implementations of abstract methods there simply is nothing to be overriden and the annotation would be ambiguous IMO.
Agreed. @Override should be used only for concrete overriden methods, not abstract implemented ones.
-- Thiago H. de Paula Figueiredo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
