Summary: | Unoptimal deprecation diagnosis | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.1 | ||
Target Milestone: | 3.0 M1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Philipe Mulet
2003-05-13 05:56:06 EDT
We are now skipping over deprecated methods if we find another inherited interface method which 'hides' the deprecated one. There is no performance side affect in non-problem cases. BUT we will not report a problem on X when implements K & J as in: class X implements K, J +- foo() interface K implements I interface J implements I +- foo() ---> should complain about overriding deprecated method /** @deprecated */ interface I +- foo() Verified. |