Bug 196653 - [compiler] More resilience with unbound caught exceptions
Summary: [compiler] More resilience with unbound caught exceptions
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.4 M1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-16 10:23 EDT by Philipe Mulet CLA
Modified: 2007-09-03 11:35 EDT (History)
1 user (show)

See Also:


Attachments
Proposed patch (6.81 KB, patch)
2007-07-16 12:15 EDT, Philipe Mulet CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2007-07-16 10:23:17 EDT
Build 3.3.0

In following code, observe that resilience on catch block variable is not as good as for standard local variable with unbound type.

public class X {
	void bar() {
		try {
			Zork z = null;
			z.foo();
		} catch(Zork z) {
			z.foo();
		}		
	}
}

The unbound exception type shouldn't block the variable from being declared, so that secondary errors are avoided.
Comment 1 Philipe Mulet CLA 2007-07-16 12:15:51 EDT
Created attachment 73861 [details]
Proposed patch
Comment 2 Philipe Mulet CLA 2007-09-03 10:43:07 EDT
Released for 3.4M1.

(was released for 3.4M1, but bug remained open - my fault)
Comment 3 Jerome Lanneluc CLA 2007-09-03 11:35:53 EDT
Verified for 3.4M1 using build I20070809-0010.