Bug 26950 - DOM/AST isLocal() could be improved to be more efficient
Summary: DOM/AST isLocal() could be improved to be more efficient
Status: RESOLVED WONTFIX
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: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2002-11-22 10:20 EST by Olivier Thomann CLA
Modified: 2009-08-30 02:35 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 Olivier Thomann CLA 2002-11-22 10:20:38 EST 
Using 1119, isLocal() only answers true for local classes directly inside a
method declaration. Its member classes don't reply true to isLocal().
Therefore there is no efficient way to find out that a class should be included
in an import statement for example.
We might want to change the API specification of the isLocal() method or add a
new method which would improve this.
This problem is related to an issue in bug 26452.
Comment 1 Olivier Thomann CLA 2002-12-04 08:23:39 EST 
isLocal() definition should be related to the semantic of a local class. A local
class cannot have static fields, etc. The actual specification doesn't make this
distinction and it should.
Comment 2 Philipe Mulet CLA 2003-01-30 15:03:59 EST 
Defer
Comment 3 Eclipse Webmaster CLA 2009-08-30 02:35:29 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.