Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.erje.net!us.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Mike Amling <mamling@chaff.us>
Newsgroups: comp.lang.java.programmer
Subject: Re: praise
Date: Tue, 04 Mar 2014 13:06:26 -0600
Lines: 22
Message-ID: <bnmmbqF9ugmU1@mid.individual.net>
References: <praise-20140225152547@ram.dialup.fu-berlin.de> <b19ab8ff-6c01-4435-a38e-ab2b92dd584d@googlegroups.com> <lejdhe$9m5$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net 1Komv/fhv4HfP/93ek0LVgb/U+JT+iyTjXNocdRRCydHL1cImG
Cancel-Lock: sha1:CWd6mhD4ctiwE9XLTZDdcVkbICI=
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
In-Reply-To: <lejdhe$9m5$1@dont-email.me>
Xref: csiph.com comp.lang.java.programmer:27681

On 2/25/14 6:46 PM, markspace wrote:
> It would be an interesting experiment to try to write some code to
> reproduce the case where a ctor is called before its initialization.

class Foo {
  static Foo baz=new Foo();
  static Object what=new Object();

  Foo() {
   System.out.println(what);
  }
}

It's easy enough to run a constructor before class initialization is 
complete. Offhand, I don't see how one would run a constructor before 
class initialization begins.

Mike Amling
--
"We will bury you." -Nikita Kruschev

Nikita Kruschev is buried at Novodevichy Cemetery, Moscow.