Re: [PHP-DEV] [RFC][DISCUSSION] - Disallow Multiple Constructor Calls

2017-01-17 Thread Nikita Popov
On Tue, Jan 17, 2017 at 9:52 PM, Fleshgrinder wrote: > On 1/17/2017 9:48 PM, Nikita Popov wrote: > > Without putting a lot of though into this, the restriction sounds > > reasonable. > > > > However, it is not immediately clear to me how this can be implemented > > without adding a disproportiona

Re: [PHP-DEV] [RFC][DISCUSSION] - Disallow Multiple Constructor Calls

2017-01-17 Thread Fleshgrinder
On 1/17/2017 10:11 PM, Tim Bezhashvyly wrote: > Hi Marcio, > > there is no deprecation because nothing is deprecated. This is a > behavioural constrain. > > Regarding parent() this is just one possible future RFC. Our > intention was just to depict that the RFC in hand opens such > possibilities.

Re: [PHP-DEV] [RFC][DISCUSSION] - Disallow Multiple Constructor Calls

2017-01-17 Thread Tim Bezhashvyly
Hi Marcio, there is no deprecation because nothing is deprecated. This is a behavioural constrain. Regarding parent() this is just one possible future RFC. Our intention was just to depict that the RFC in hand opens such possibilities. There is no obligation. Regards, Tim > On 17 Jan 2017, at

Re: [PHP-DEV] [RFC][DISCUSSION] - Disallow Multiple Constructor Calls

2017-01-17 Thread Marcio Almada
Hi Tim, I'm ok with the idea. But could you elaborate why not propose a deprecation before the error on PHP 8? Also, one point about the future scope "Add shorthand parent() as alternative to parent::__construct().": Do we really need to introduce more language constructs that look like valid use

Re: [PHP-DEV] [RFC][DISCUSSION] - Disallow Multiple Constructor Calls

2017-01-17 Thread Fleshgrinder
On 1/17/2017 9:48 PM, Nikita Popov wrote: > Without putting a lot of though into this, the restriction sounds > reasonable. > > However, it is not immediately clear to me how this can be implemented > without adding a disproportionate amount of overhead for something which I > would consider a rat

Re: [PHP-DEV] [RFC][DISCUSSION] - Disallow Multiple Constructor Calls

2017-01-17 Thread Tim Bezhashvyly
Hi Nikita, thank you for your feedback. Would you suggest to convert RFC into prohibition of explicit __construct calls except parent::__construct? Regards, Tim > On 17 Jan 2017, at 21:48, Nikita Popov wrote: > > On Tue, Jan 17, 2017 at 9:17 PM, Tim Bezhashvyly

Re: [PHP-DEV] [RFC][DISCUSSION] - Disallow Multiple Constructor Calls

2017-01-17 Thread Nikita Popov
On Tue, Jan 17, 2017 at 9:17 PM, Tim Bezhashvyly wrote: > Dear internals, > > me and Richard Fussenegger came up with a RFC draft disallowing multiple > constructor calls - https://wiki.php.net/rfc/ > disallow-multiple-constructor-calls disallow-multiple-constructor-c

Re: [PHP-DEV] [RFC][DISCUSSION] - Disallow Multiple Constructor Calls

2017-01-17 Thread Marco Pivetta
Hey Tim, On Tue, Jan 17, 2017 at 9:17 PM, Tim Bezhashvyly wrote: > Dear internals, > > me and Richard Fussenegger came up with a RFC draft disallowing multiple > constructor calls - https://wiki.php.net/rfc/ > disallow-multiple-constructor-calls disallow-multiple-con

[PHP-DEV] [RFC][DISCUSSION] - Disallow Multiple Constructor Calls

2017-01-17 Thread Tim Bezhashvyly
Dear internals, me and Richard Fussenegger came up with a RFC draft disallowing multiple constructor calls - https://wiki.php.net/rfc/disallow-multiple-constructor-calls Here is a Reddit discussion thread - https://www.reddit.com/