Bug 124148 - [1.5][compiler] Deprecation check should be more lazy
Summary: [1.5][compiler] Deprecation check should be more lazy
Status: RESOLVED DUPLICATE of bug 95056
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M5   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-17 10:56 EST by Philipe Mulet CLA
Modified: 2006-01-18 12:45 EST (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 2006-01-17 10:56:59 EST 
3.2m4

The deprecation checks is causing entire annotations to be resolved, in case it contains @Deprecated. This is not efficient in term of lazyness, as in most cases it is resolving irrelevant information eagerly then.

There should be a way to peak at annotation for a reference to Deprecated, and only resolve this portion to answer the deprecation check.
Comment 1 Philipe Mulet CLA 2006-01-18 11:53:16 EST 
Introduced: Binding#initializeDeprecatedAnnotationTagBits()
too only find out if annotation contains a reference to java.lang.Deprecated.
Comment 2 Philipe Mulet CLA 2006-01-18 12:45:52 EST 
Actually, closing as dup, since bug 95056 was already mentionning same fix.

*** This bug has been marked as a duplicate of 95056 ***