Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110262
MIME-Version: 1.0
References: <CAJd4=YZd3Mh8sQjYxE-YfNim-CN1+j8oST2W+nykXDynC_KQiA@mail.gmail.com>
 <CADyq6sKn7ERUTmHfOSt6bOeWvFiS33ciaK7WZuLgktCs7AN3zg@mail.gmail.com> <CA+hqhpeSAMK6nyig+J69s8=OsGWusyVjOPX=i+wQ+6oz=vtcxQ@mail.gmail.com>
In-Reply-To: <CA+hqhpeSAMK6nyig+J69s8=OsGWusyVjOPX=i+wQ+6oz=vtcxQ@mail.gmail.com>
Date: Fri, 22 May 2020 22:18:52 +0200
Message-ID: <CADyq6sJ1gF+nKWKEUkdVfrAuxagiiXJJ-Dv64i3piZ7Ze3O5Jg@mail.gmail.com>
To: Bruce Weirdan <weirdan@gmail.com>
Cc: =?UTF-8?Q?Pedro_Magalh=C3=A3es?= <mail@pmmaga.net>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000034d79005a64257bb"
Subject: Re: [PHP-DEV] [RFC] [Discussion] Remove inappropriate inheritance
 signature checks on private methods
From: ocramius@gmail.com (Marco Pivetta)

--00000000000034d79005a64257bb
Content-Type: text/plain; charset="UTF-8"

Hey Bruce,


On Fri, May 22, 2020, 22:07 Bruce Weirdan <weirdan@gmail.com> wrote:

>
> On Fri, May 22, 2020 at 7:26 PM Marco Pivetta <ocramius@gmail.com> wrote:
>
>> Overall, this RFC breaks some design capabilities that are within the
>> language, specifically around `__`-prefixed methods in the language.
>
>
> Wouldn't your use cases be covered by `protected final` though, as
> proposed by Pedro?
>

This design is made appositely to prevent the child class from being able
to call the constructor: the only viable constructors are the named
constructors on the supertype

>

--00000000000034d79005a64257bb--