Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78937
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain tutteli.ch designates 80.74.154.78 as permitted sender)
To: "'Stanislav Malyshev'" <smalyshev@gmail.com>,
	"'PHP Internals'" <internals@lists.php.net>
References: <546B0F62.1090705@gmail.com>
In-Reply-To: <546B0F62.1090705@gmail.com>
Date: Tue, 18 Nov 2014 11:03:26 +0100
Message-ID: <004301d00316$e62a7390$b27f5ab0$@tutteli.ch>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQHw1mEV3fPWLk1MjvqQ7S56C1C5CZwkfbtg
Content-Language: de-ch
Subject: AW: [PHP-DEV] [RFC] Default constructors
From: php@tutteli.ch ("Robert Stoll")

> -----Urspr=C3=BCngliche Nachricht-----
> Von: Stanislav Malyshev [mailto:smalyshev@gmail.com]
> Gesendet: Dienstag, 18. November 2014 10:21
> An: PHP Internals
> Betreff: [PHP-DEV] [RFC] Default constructors
>=20
> Hi!
>=20
> I'd like to propose the following RFC, which in short would allow any =
method to call parent ctor (and some other methods)
> even if such is not explicitly defined:
>=20
> https://wiki.php.net/rfc/default_ctor
>=20
> The reasons are outlined in detail in the RFC and here:
> http://php100.wordpress.com/2014/11/04/default-constructors/
>=20
> The patch is not finished yet but seems to be working fine, I'll add =
it to the RFC this week as soon as I finish it. I'd like to put
> idea out there in the meantime and hear what everybody thinks about =
it.
>=20
> Thanks,
> Stas
>=20
> --
> PHP Internals - PHP Runtime Development Mailing List To unsubscribe, =
visit: http://www.php.net/unsub.php

+1
And concerning the subtle BC break, I think it is a bug that bar is =
currently not executed. In other cases where superfluous arguments are =
provided, they are evaluated. Hence, inconsistent anyway and should be =
fixed IMO.
Another example which outlines that the new behaviour is more =
appropriate:

class Foo{}
$b =3D 0;
//left over from refactoring, $b is currently not incremented even =
though it looks like that, new behaviour would fix that
$a =3D new Foo(++$b);=20