Re: gcj/148: Definite assignment problem

[Bryce McKinlay <bryce at albatross dot co dot nz>]

The following reply was made to PR gcj/148; it has been noted by GNATS.

From: Bryce McKinlay <bryce@albatross.co.nz>
To: green@cygnus.com, java-gnats@sourceware.cygnus.com
Cc:  
Subject: Re: gcj/148: Definite assignment problem
Date: Wed, 16 Feb 2000 22:13:31 +1300

 Somewhat related - I'm getting the "Variable may not have been
 initialized" message from the latest compiler from cvs in totally bogus
 situations that used to work fine. This bug seems to have appeared
 recently (certainly since 19991213 which is the second-most-recent build
 I have lying around)
 
 In my case I have
 
 String var_value = line.substring(...);
 Variable v = new Variable(first_token, var_value.trim(),  ...);
 
 and the compiler is telling me that var_value may not have been
 initialized. I'm going to try and come up with a test case...
 
   [ bryce ]
 
 
 green@cygnus.com wrote:
 
 > >Number:         148
 > >Category:       gcj
 > >Synopsis:       Definite assignment problem
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    apbianco
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Sun Feb 13 09:40:02 PST 2000
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Anthony Green
 > >Release:        Latest cvs
 > >Organization:
 > >Environment:
 > Red Hat Linux 6.1
 > >Description:
 > The compiler is not recognizing a situation
 > where a variable is guaranteed to be assigned to,
 > and is exiting with a definite assignment error.
 > >How-To-Repeat:
 > I've checked in a test case: libjava.compile/assignment.java
 > >Fix:
 >
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted: