No @Override on methods from an interface; they show up as errors on some
compilers (depending on how you have things set up).
@Overrides is an annotation designed to freak out when a super class changes
(so you notice that it changes).
Interfaces already have a compile error produced in this case (change the
interface method and all children break until they are fixed).
Jody
On Tue, Jul 26, 2011 at 12:36 PM, Michael Bedward <[email protected]
> wrote:
> Hi folks,
>
> Just want to check on coding style following the move to Java 6.
>
> Should we always put an @Override annotation on methods implemented
> from an interface in new GeoTools code now ? And should we add the
> annotation to existing code ?
>
> Michael
>
>
> ------------------------------------------------------------------------------
> Magic Quadrant for Content-Aware Data Loss Prevention
> Research study explores the data loss prevention market. Includes in-depth
> analysis on the changes within the DLP market, and the criteria used to
> evaluate the strengths and weaknesses of these DLP solutions.
> http://www.accelacomm.com/jaw/sfnl/114/51385063/
> _______________________________________________
> Geotools-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
