On Thu, Jun 28, 2012 at 11:56 AM, Robert Zeigler < [email protected]> wrote:
> But in the case of interfaces, if you've misspelled the method name, the > compiler will complain that you haven't implemented the interface... > > ... unless you are creating an abstract base class. > That said, I'm not sold by the argument of "@Override is for overriding of > concrete methods" since you can use @Override for overriding abstract > methods. So why not interface methods? > > Robert > > On Jun 28, 2012, at 6/281:42 PM , Kalle Korhonen wrote: > > > On Thu, Jun 28, 2012 at 6:51 AM, Thiago H de Paula Figueiredo > > <[email protected]> wrote: > >> On Wed, 27 Jun 2012 18:16:03 -0300, Ulrich Stärk <[email protected]> > wrote: > >> Agreed. @Override should be used only for concrete overriden methods, > not > >> abstract implemented ones. > > > > A pragmatic approach is that @Override helps catching misspellings in > > the method names and that's good enough reason for me to use @Override > > on interface methods. > > > > Kalle > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
