🚀 go-pugleaf

Thanks Tor! You passed the test!
The following illustrates the problem even better if you understand what is
going on:

class  A
{
  static String str = new String("init: ");
  static { str += "a";
         }
}

class  B extends A
{ static String str2 = new String("xx");
  static { str += "b";
         }
}

public class Test
{ public static void main(String[] args)
{ //  System.out.println(B.str2);
    System.out.println(B.str);
  }
}

The first (preceded by //) forces class B to be loaded, firing the static
initializer of B
You would think any reference to B would do this, but that obviously is not
the case.

Nevertheless it seems that the java performance bunch forgot about the
static initializers when they implemented an optimizing feature like this!
It scares the hell out of me: What about new versions of the VM?
I havent read the language spec completely but I fear that nothing is said
about this all since it is a compiler feature: optimizing code, forgetting
about static initializers. (I think this is the only scenario; using static
initializers; where such an optimization causes problems)

'Guess I stumbled into one of the dark corners of Java here..

Wido