Bug 124148

Summary:	[1.5][compiler] Deprecation check should be more lazy
Product:	[Eclipse Project] JDT	Reporter:	Philipe Mulet <philippe_mulet>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.2
Target Milestone:	3.2 M5
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Philipe Mulet

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

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

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 ***