[
https://issues.apache.org/jira/browse/MAHOUT-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588093#action_12588093
]
Karl Wettin commented on MAHOUT-34:
-----------------------------------
{quote}
And Override, although not a big issue, is something I use with this
understanding:
If I ever add a new method to an interface, the compiler can help me add it to
every subclass by generating appropriate errors and pointing me to those
missing places. However, if I remove a function from an interface, the compiler
can no longer help me. I'll have to manully find the subclasses implementing
that method and see if it should be removed. So for me, the @Override
annotation gives the compiler a mechanism to complain if that method is missing
from the interfaces/superclass, like the overrides keyword in C# and other
languages. This is why I always use @Override even if I am just implementing a
method, as long as a superclass/interface names it. If that's not what the
annotation was designed for, I'll remove it.
{quote}
This is exactly how JDK1.6 works. JDK1.5 that Mahout use allows @Override in
generalized super classes but not too much in the polymorphic scope.
I.e. @Override is not valid for a top level interface method implementations,
nor in interfaces that extend other interfaces.
Or at least, that is how I understand the situation.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5008260
> Iterator interface for Vectors
> ------------------------------
>
> Key: MAHOUT-34
> URL: https://issues.apache.org/jira/browse/MAHOUT-34
> Project: Mahout
> Issue Type: New Feature
> Reporter: Samee Zahur
> Assignee: Karl Wettin
> Attachments: VectorIterator.3.patch.bz2,
> VectorIterator.patch.2.tar.bz2, VectorIterator.patch.tar.bz2
>
>
> Implemented an Iterator interface for the Vector classes. Was necessary for
> porting from Float[] used in some parts of the code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
