Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118406
MIME-Version: 1.0
References: <CABigaAWAMfjTh9FBhu-SQRfu9_pgqt5pp7uj4kmNg0QmXbnS-Q@mail.gmail.com>
 <62f3da67.810a0220.ed5e8.1b2cSMTPIN_ADDED_MISSING@mx.google.com>
 <CALKiJKqjLqwyC+5zyfo=NaeZpyGRv8K4_dzQ7fRtH_48j9Hciw@mail.gmail.com>
 <CABigaAUNweFCnDryt8yZ4m2Cn3Rn8HACNVxvj+RvxrPFets5vw@mail.gmail.com> <17C7EF67-298D-40E8-A872-5A9D78A7EEDA@gmail.com>
In-Reply-To: <17C7EF67-298D-40E8-A872-5A9D78A7EEDA@gmail.com>
Date: Thu, 11 Aug 2022 00:23:44 +0200
Message-ID: <CADK1yXLVqD2hfuj66VZAgfhPXnZUOdB-nEy82H=YA+UKUyK-Kw@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002a4e7305e5ea8184"
Subject: Re: [PHP-DEV] Re: [Concept] Extension methods
From: deleugyn@gmail.com (Deleu)

--0000000000002a4e7305e5ea8184
Content-Type: text/plain; charset="UTF-8"

On Wed, Aug 10, 2022, 11:30 PM Rowan Tommins <rowan.collins@gmail.com>
wrote:

>
> To be honest, I put them in that order more for "purity" reasons: if they
> come before __call, they can change the existing behaviour of the class, by
> defining an extension method with the same name as a "virtual" method
> implemented with __call. That then becomes a very different feature.
>

I would argue in favor of extension having precedence over __call because
1) classes with __call wouldn't be able to be `extended` and 2) extensions
could actually "fix" the ~ab~use of some use of __call. I suppose this
would allow me to write an Extension that mimics the exact behavior of
__call and actually avoid __call from being hit while still keeping the
same behavior of the class.

--0000000000002a4e7305e5ea8184--