Bugzilla – Full Text Bug Listing
| Summary: | Options of Content Assistent throws clause of method header | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Paramasivam <paramasivam.kaliyamoorthi> | ||||
| Component: | Core | Assignee: | David Audel <david_audel> | ||||
| Status: | VERIFIED WONTFIX | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | Olivier_Thomann, paramasivam.kaliyamoorthi, srikanth_sankaran | ||||
| Version: | 3.5 | ||||||
| Target Milestone: | 3.6 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Exceptions classes are proposed first in the list of proposals because the user probably want to complete the name of a top level type exception. But the user could want to complete the name of a type which contains the declaration of an exception. As this case is less common, these proposals are proposed at the end of the list. eg. the user type: void foo() throws TopLevelTyp| //ctrl+space at | because he want to write; void foo() throws TopLevelType.InnerException Another reason to propose all types is because currently the content assist processor recognize exceptions by their names. If the name contains 'Exception' or 'Error' the type is considered as an exception. This is because content assist must be quick and it is too costly to compute the hierarchy of each type. So to not miss an exception without 'Exception' or 'Error' in its name, all types are proposed. The current behavior works as expected so i close this bug as WONTFIX. Verified for 3.6M1 |
Created attachment 116642 [details] screen shot of might be enhanced content assistent Regarding content assistant --------------------------- When i press Ctrl + Space bar after "throws" clause of a method header, show only Exception classes rather than all the matching options Please see the attachment