Summary: | NPE in Code Assist | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Peter Burka <peter_burka> |
Component: | Core | Assignee: | David Audel <david_audel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | CC: | Olivier_Thomann |
Version: | 2.0 | ||
Target Milestone: | 2.0 M6 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Peter Burka
2002-05-14 17:24:00 EDT
looks like parameterTypeNames or parameterNames is null. According the javadoc this should not occur. We can make the result collector code robust, but to know for how to handle this case we should now when this happens, i.e., should such a proposal be ignored, shown without a parameters? If it should be ignored can CORE not propose it in the first place. Moving to JDT CORE The problem occur when a parameter type of a binary method is unresolved. The bugs is in BinaryTypeBinding#availableMethods. The correct code must be 'return availableMethods;' and not 'return methods;' Fixed. |