🚀 go-pugleaf

Tom.Eugelink@OVSoftware.com writes:

> It seems to me there is no reason why the declares shouldn't be
> executed when the constructor is entered instead of just before the
> first line in the constructor...

Your _actual_ problem is that fireman.display() _masks_
person.display(), and methods are invoked dynamically.

It's a flaw in the program design, not the language: You should not
invoke methods that are not private or final in a constructor of a
non-final class, because a subclass can override it - like in your
example. Basically, superclass constructor invocation goes before any
initialization of fields in the subclass, which leads to the
NullPointerException in your example.