Re: "final" bug??

From:

Roedy Green <see_website@mindprod.com.invalid>

Newsgroups:

comp.lang.java.programmer

Date:

Sat, 02 May 2009 15:16:56 -0700

Message-ID:

<mdhpv4hd9g0tpav131030gplsc94v9htna@4ax.com>

On Sat, 02 May 2009 17:15:21 -0400, Lew <noone@lewscanon.com> wrote,
quoted or indirectly quoted someone who said :

Regardless, the fix is simple:

static final String allPads;
static
{
   String ap;
   try
   {
     aP = HunkIO.readEntireFile( ALLPADS_FILE );
   }
   catch ( IOException e )
   {
     err.println( "Unable to access "+ ALLPADS_FILE );
     aP = null;
   }
   allP

That sounds counter intuitive. If ap is ambiguously assigned in the
same pattern, so much be allp???

I'd think you might have to do:

String ap = null;

I will experiment.

That's for the tip. This has been very infuriating, because the
automated refactoring tools alternate between putting the final in and
out like Oscar Wilde with a comma.
--
Roedy Green Canadian Mind Products
http://mindprod.com

"Species evolve exactly as if they were adapting as best they could to a changing world, and not at all as if they were moving toward a set goal."
~ George Gaylord Simpson