On Thu, Jun 28, 2012 at 11:42 AM, Kalle Korhonen <[email protected] > 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. > Yes, that's why I favor it in this way. Really, Java should have had an override keyword and an implement keyword. > > Kalle > > --------------------------------------------------------------------- > 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
