Bug 3282 - JCK 1.4 - DASG - assigned variable before catch block after return statement (1GK2AHX)
Summary: JCK 1.4 - DASG - assigned variable before catch block after return statement ...
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:52 EDT by Olivier Thomann CLA
Modified: 2002-01-11 09:04 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Thomann CLA 2001-10-10 22:52:32 EDT 
http://www.ott.oti.com/uvm/OTIIBM/numbat/Testing/JCK-
14/tests/lang/DASG/dasg156/dasg15601m3/dasg15601m3.html: dasg15601m3 - assigned 
variable before catch block after return statement 
    http://www.ott.oti.com/uvm/OTIIBM/numbat/Testing/JCK-
14/tests/lang/DASG/dasg156/dasg15601m5/dasg15601m5.html: dasg15601m5 - assigned 
variable before catch block after break statement 
    http://www.ott.oti.com/uvm/OTIIBM/numbat/Testing/JCK-
14/tests/lang/DASG/dasg156/dasg15601m6/dasg15601m6.html: dasg15601m6 - assigned 
variable before catch block after continue statement

	Test case:

NOTES:
OT (14/09/2001 5:13:39 PM)
	javac 1.4 reports:
dasg15601m3.java:23: variable a1 might already have been assigned to
                                c = (a1=6) + 1;
                                     ^
OT (14/09/2001 5:15:08 PM)
	Other test cases corresponding to other PRs:
	javac 1.3 fails as well.

PM (9/20/2001 6:00:19 PM)
	This one looks like a bug in Jdk1.4.
Comment 1 Philipe Mulet CLA 2001-10-17 09:30:33 EDT 
Actually Javac 1.3 did implement the same behavior. The rational is that 
pessimistic bytecode analysis (e.g. binary compatibility) requires the
compiler to reject such code.

Fixed