Community
Participate
Working Groups
In this case BB.test does not override AA.test, but its tagged in the editor that it does. class AA<T> { public AA<Object> test() { return null; } } class BB extends AA<CC> { public <T> BB test() { return null; } } class CC {}
The editor uses the info provided by the bindings. But moving to text to make sure.
I'm using the helper methods from JDT UI. Same problem with override decorator.
Martin, can you please have a look and move on the JDT/Core if we simply call the methods on core.
we're still using our homebrewed 'override' check. Markus, what are the latest news on 'MethodBinding.overrides()' ?
No news lately. Methods IMethodBinding#overrides(..) and #isSubsignature(..) are currently not used because they don't work across binding environments. However, they're implemented and should work for bindings from one compiler loop, but they have not been tested "in the field".
We should try to switch and use the jdt.core infrastructure here.
fixed > 20050606
I've reverted the change in Bindings.findOverriddenMethodInType(..), since it cause 4 failing TypeMismatchQuickFixTests. The old implementation did not check return types, but IMethodBinding#overrides(..) does.
not for 3.1. IMethodBinding.override is not yet used, its too late to start testing this now.
Martin, we should investigate whether this can be fixed for 3.1.1. A similar bug is 100233. We should either switch to the core method here (which results in some fuzzyness we had regarding the return type) or add this case to the Bindings implementation we have right now.
Martin, Markus can you please coordinate the fix for 97927 & 100233. IMO they will affect the same method(s) in class Bindings.
I suggest we do the fix as suggested in bug 100233. IMO, changing to IMethodBinding.override for 3.1.1 is not an option.
Martin, I opt to mark this one as a dup of 100233 if we agree on fixing 100233 for 3.1.1.
*** This bug has been marked as a duplicate of 100233 ***
