Bug 37541 - Unoptimal deprecation diagnosis
Summary: Unoptimal deprecation diagnosis
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M1   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-13 05:56 EDT by Philipe Mulet CLA
Modified: 2003-06-06 07:37 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2003-05-13 05:56:06 EDT 
Build R2.1

Only the most specific overriden deprecated method should impact the 
deprecation diagnosis generated when overriding a deprecated method.

class X implements I
 +- foo() ---> should not complain about overriding deprecated method

interface I implements J
 +- foo() ---> should complain about overriding deprecated method

/** @deprecated */
interface J
 +- foo()
Comment 1 Kent Johnson CLA 2003-05-13 16:49:23 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()
Comment 2 David Audel CLA 2003-06-06 07:37:02 EDT 
Verified.