Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113405
To: internals@lists.php.net
References: <CAF+90c-HY-0fx+pTmntRJZKcQcZFfk3uJwrZ6FAMAx5_Wj+JHw@mail.gmail.com>
 <60437107.1c69fb81.c3486.ac89SMTPIN_ADDED_MISSING@mx.google.com>
Message-ID: <5fe3212f-e48e-9d17-1851-19a8855fcc6d@gmail.com>
Date: Sat, 6 Mar 2021 13:28:34 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <60437107.1c69fb81.c3486.ac89SMTPIN_ADDED_MISSING@mx.google.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] Re: [RFC] New in initializers
From: rowan.collins@gmail.com (Rowan Tommins)

On 06/03/2021 12:09, Andrea Faulds wrote:
> This seems reasonable, but I fear it would create a similar mess to 
> C++ with static initialisers, because a class constructor can do 
> basically anything… 


That was my initial reaction, too, but it's actually pretty trivial to 
do static initialisation already, thanks to the way autoloading works. 
For instance if you put the below in "Foo.php", then it will be run once 
the first time class "Foo" is loaded:

class Foo {
    public static $bar;
}

Foo::$bar = new Whatever();


This has essentially the same effect as writing this:

class Foo {
    public static $bar = new Whatever();
}


Which is absolutely horrible if Whatever's constructor has side effects, 
but then most things are going to be horrible if your constructors have 
side effects...

Regards,

-- 
Rowan Tommins
[IMSoP]