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 22:08, Marcio Almada <marcio.w...@gmail.com> wrote: > > 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 > user space code https://3v4l.org/CE2q8 <https://3v4l.org/CE2q8> ? > > Thanks. > Márcio. > > 2017-01-17 16:17 GMT-04:00 Tim Bezhashvyly <tim.bezhashv...@gmail.com > <mailto:tim.bezhashv...@gmail.com>>: > 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 > <https://wiki.php.net/rfc/disallow-multiple-constructor-calls> > <https://wiki.php.net/rfc/disallow-multiple-constructor-calls > <https://wiki.php.net/rfc/disallow-multiple-constructor-calls>> > > Here is a Reddit discussion thread - > https://www.reddit.com/r/PHP/comments/5okdac/php_rfc_disallow_multiple_constructor_calls/ > > <https://www.reddit.com/r/PHP/comments/5okdac/php_rfc_disallow_multiple_constructor_calls/> > > <https://www.reddit.com/r/PHP/comments/5okdac/php_rfc_disallow_multiple_constructor_calls/ > > <https://www.reddit.com/r/PHP/comments/5okdac/php_rfc_disallow_multiple_constructor_calls/>> > > Any suggestions are highly welcome. Thank you. > > Regards, > Tim > > >
