Hi all,
On Sun, Jan 11, 2015 at 9:34 AM, Stanislav Malyshev
wrote:
> I'd like to initiate a vote on this RFC:
> https://wiki.php.net/rfc/default_ctor
>
> TLDR: this RFC would make a call to parent::__construct() succeed (as in
> "not produce a fatal error") even if the parent class does not defi
Le 11/01/2015 01:34, Stanislav Malyshev a écrit :
I'd like to initiate a vote on this RFC:
https://wiki.php.net/rfc/default_ctor
Hi,
After discussing this RFC with other people of AFUP, we would be +1 on
this, by a small margin.
On one side, being able to always call a parent constructor wi
> De : Stanislav Malyshev [mailto:smalys...@gmail.com]
>
> TLDR: this RFC would make a call to parent::__construct() succeed (as in
> "not produce a fatal error") even if the parent class does not define a
> ctor. Same for __destruct and __clone. The motivation for it is in the
> RFC and here: http
Hi Stas,
On Sun, Jan 11, 2015 at 9:34 AM, Stanislav Malyshev
wrote:
> I'd like to initiate a vote on this RFC:
> https://wiki.php.net/rfc/default_ctor
>
> TLDR: this RFC would make a call to parent::__construct() succeed (as in
> "not produce a fatal error") even if the parent class does not def
Hi!
I'd like to initiate a vote on this RFC:
https://wiki.php.net/rfc/default_ctor
TLDR: this RFC would make a call to parent::__construct() succeed (as in
"not produce a fatal error") even if the parent class does not define a
ctor. Same for __destruct and __clone. The motivation for it is in th
