Description Richard 2010-07-15 17:38:18 EDT

Build Identifier: I20100608-0911

The flow analysis from the compiler does not recognize that in that case

public class Test {

    public static void main(String[] args) {
	    Integer tmp;
	    tmp = new Integer(5);
	    Object o;
	    if (tmp instanceof Integer)
	    {
	        o = (Integer)tmp;
	    }
	    else
	    {
	        {if (true) throw new RuntimeException();}
	    }
	    System.out.println(o);
    }
 }

o will always be initialized when reaching the System.out.println statement. I think that this may strictly spoken not be bug as the JLS would allow to classify it as error, but previous eclipse versions compile the code without complaint. 

[[The actual problem occurs for me in generated code and has to be "work-arounded" each time.]]

Reproducible: Always

Steps to Reproduce:
1.Compiling class 
public class Test {

    public static void main(String[] args) {
	    Integer tmp;
	    tmp = new Integer(5);
	    Object o;
	    if (tmp instanceof Integer)
	    {
	        o = (Integer)tmp;
	    }
	    else
	    {
	        {if (true) throw new RuntimeException();}
	    }
	    System.out.println(o);
    }
    
}
in eclipse 3.6 fails with the error message "o may not be initialised", but works fine with (at least) eclipse 3.5 
2.
3.