Bugzilla – Full Text Bug Listing
| Summary: | [assist] Missing proposals in some catch blocks. | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Srikanth Sankaran <srikanth_sankaran> |
| Component: | Core | Assignee: | Ayushman Jain <amj87.iitr> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
Ayush, please follow up. This is not a 1.7 item as the behavior is same even at 1.6 compliance. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
import java.io.IOException; As the comments below show, completing at the last | does not propose RunTimeException and Exception while completing at the prior | does. This looks suspicious and needs to be understood. import javax.naming.OperationNotSupportedException; public class Abc { static void foo() throws IOException, IllegalArgumentException, OperationNotSupportedException, IndexOutOfBoundsException { } void bar() { try { Abc.foo(); } catch (IOException e) { } catch (OperationNotSupportedException e) { } catch (IllegalArgumentException e) { } catch (| e) { // RunTimeException proposed here } catch (| e) { // but not here } } }