Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85792
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.44 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <006d01d07603$3a104a70$ae30df50$@php.net>
References: <CB.90.41712.5B6CB255@pb1.pair.com>
	<006d01d07603$3a104a70$ae30df50$@php.net>
Date: Mon, 13 Apr 2015 16:16:11 -0600
Message-ID: <CAFMT4NrKCXn8CPxhQO_4T5N_uGJDAqdFEgh3DF6wYU6HwY5taw@mail.gmail.com>
To: "francois@php.net" <francois@php.net>
Cc: Johannes Ott <mail@deroetzi.de>, internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] New RFC draft "static class constructor"
From: levim@php.net (Levi Morrison)

> - IMO, the method should be called when the class is created, just after every parent class and implemented interfaces are created.

In general I think static class data and static class constructors are
a sign of poorly designed code, which means I am against this feature.
If it does make it though I agree with this statement above. The
behavior proposed in the RFC makes it non-obvious when the class
constructor is run and would much prefer it happening immediately
after definition.