Class initialization

Question

In the assertion guide,
http://java.sun.com/j2se/1.4.1/docs/guide/lang/assert.html#design-faq-enable-disable
the following question (8) is presented.
"Why does an assert statement that executes before its class is initialized behave as if assertions were enabled in the class?"
The answer begins
"Few programmers are aware of the fact that a class's constructors and methods can run prior to its initialization."
Would you please explain this sentence (independent of the question)?

Answer 1

Yet the exerpt states the reverse - That the
constructors and methods can be called before the
class is initialised.
This shows a static method running a static method,
but construction still occurs after the static
initialisers have. Do they perhaps mean that instance
initialisers may not have been run before the
constructor completes? This is certainly possible if
an overridden method is invoked in a super constructor
or super class instance initialiser.
How could you instantiate a class without the static
initialisation having occurred (class
initialisation).
I thought it was obvious but the following one should be more so. Note that the class (nothing to do with an instance) is not initialized until the static initializer completes.
And again I want to point that if this happens in real code then the most likely reason is because of a bug or because the design is wrong. The chance of finding a legitimate reason to have code like this is zero in my mind.
    public class TTest
        public static void main(String[] args)
    TTest()
        System.out.println("Now in the constructor");
    static
        System.out.println("Start the static initializer");
        reallyStupid();
        System.out.println("End the static initializer");
    static private boolean isDone;
    private static void reallyStupid()
        System.out.println("really stupid thing to do");
        if (!isDone)
            isDone = true;
            TTest t = new TTest();
  The output is...
  Start the static initializer
  really stupid thing to do
  Now in the constructor
  End the static initializer