Summary: | ICompilationUnit should provide a getImport(..) method that uses the simple name | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Vikas Trivedi <vtrivedi> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 3.0 | ||
Target Milestone: | 3.3 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Vikas Trivedi
2004-03-10 17:53:17 EST
Will reconsider post 3.0 Why don't you simply iterate all imports using ICompilationUnit#getImports() and play whatever logic you want ? #getImport(...) is spec'ed as a convenience method (ie. helper), and all you are asking is a further subsequent helper method, which in my opinion doesn't add much value, since it must answer a collection/array of matching candidate, which is just allocating one extra array etc... Basically, this cannot be blocking you; suggest you provide a patch for what you really have in mind; and if killer functionality addition, then we may consider it. If not, then we will leave it to client to play whatever semantics when iterating imports. This is similar to our rules for navigating throughout the model. Talked with Vikas, he agreed with previous comment. No action planned. closing |