Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350653 - [assist] Missing proposals in some catch blocks.
Summary: [assist] Missing proposals in some catch blocks.
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ayushman Jain CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-29 02:31 EDT by Srikanth Sankaran CLA
Modified: 2019-04-05 01:19 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Srikanth Sankaran CLA 2011-06-29 02:31:02 EDT
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 
        	
        }
    }
}
Comment 1 Srikanth Sankaran CLA 2011-06-29 02:35:04 EDT
Ayush, please follow up. This is not a 1.7 item as the behavior is
same even at 1.6 compliance.
Comment 2 Eclipse Genie CLA 2019-04-05 01:19:18 EDT
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.