lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonik Seeley <yo...@lucidimagination.com>
Subject Re: svn commit: r1206916 - in /lucene/dev/branches/branch_3x: ./ lucene/ lucene/backwards/src/ lucene/backwards/src/test-framework/ lucene/backwards/src/test/ solr/ solr/core/src/java/org/apache/solr/analysis/ solr/core/src/java/org/apache/solr/schem
Date Mon, 28 Nov 2011 13:40:29 GMT
On Mon, Nov 28, 2011 at 6:19 AM, Uwe Schindler <uwe@thetaphi.de> wrote:
> And personally I don’t agree that @Override on interfaces is useful, it's itself a
bug as there is nothing overridden.

What's the practical difference between overriding an abstract method
and implementing an interface method? Neither actually override any
behavior.

> The specification and javadocs are authoritative.

And the authors clearly thought @Override for interface methods was a
good idea ;-)
I do like being able to use this feature as it makes the code easier
to understand at a glance and helps prevent bugs.

-Yonik
http://www.lucidimagination.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message