Community
Participate
Working Groups
The "unused parameters" warning would be more useful if it could limit itself to only checking private methods. Any other methods are often likely to have extra parameters because (a) they are overriding a method and they don't need the extra data (b) they are going to be overriden the overriders need the extra data Which makes this less useful than it could be, because it produces too many false positives.
Which build are you using ? Unused parameter diagnosis is ignoring method which are overriding others.
build 200303071024. That's great, but it doesn't help where I have methods that are meant to be overriden, and thus define more parameters than they actually need. Kind of like abstract methods, except that I supply an empty body so that the subclasses do not HAVE to implement them.
I agree with your point for top methods which aren't easy to isolate (JDT/Core has some warnings due to this, and there isn't much you can do for these at the moment). Only flagging private methods would be quite restrictive.
Agreed. Might be an idea to have a means of turning isolated warnings off on a per-class/method basis, perhaps using javadoc labels. But that also seems like too much effort for too little reward. Request closed.
