🚀 go-pugleaf

Consider the following:

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

class  B extends A
{ static { str += "b";
         }
}

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

This will print

init: ab

as you would expect.

But if you comment out the B instOfB = new B(); i.e. the main looks like

{ public static void main(String[] args)
 { //B instOfB = new B();
    System.out.println(B.str);
  }

this will print

init: a

Now here's the question: WHY DOES'NT THE SECOND STATIC INITIALIZER FIRE?? Is
it because the jvm decides it does not need to load the B class since it
thinks the str is defined in A and B is an A?

The certification question: (multiple multiple choice)
1) This is a Bug
2) This is a Feature
3) This is Not Defined
4) Some of the above
5) I need some asperine

I am looking forward to your answer (especially the one from Goshling)

Wido Riezebos