Strings in Switch
    Paul Benedict 
    pbenedict at apache.org
       
    Tue Dec  8 06:39:54 PST 2009
    
    
  
Joe,
> Such discrepancies and changes were long ago in a Java platform far, far
> away.  It is vanishingly unlikely that String.hashCode will change again
> in the SE platform because the "behavioral compatibility" impact would
> be too large; see
I agree the change may be unlikely, but why bet your compiler on it?
Since you are encoding the result of the hash **in the class file**, I
think it is necessary to ensure it *never* changes. Do remedies exist?
Paul
    
    
More information about the coin-dev
mailing list