Summary: | hierarchy: type hierarchy on interfaces does not contain Object | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Adam Kiezun <akiezun> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.1 M2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Adam Kiezun
2002-09-17 11:53:34 EDT
I would agree too. Current API (e.g. javadoc of ITypeHierarchy.getSupertypes(IType)) implies that if the type is an interface, only interfaces that the interface extends are returned. Asked on jdt-core-dev mailing list if there are advantages to changing this. Post from Adam on jdt-core-dev: Guys, i did not mean it - but look like my suggestion caused some trouble here and there. I do not feel strongly about it so if it is going to break somebody's code (or world <g>) then it's ok. from my side, to leave it as is. It just felt weird not to see Object when i asked an interface for its supertypes, that's all. a. Closing |