Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115776
MIME-Version: 1.0
References: <CAMrTa2HBv94ui0xGsqZwP=uL3AHQDMPAhaToo7m4F5Yh5QT64Q@mail.gmail.com>
 <2fd2d665-ca3a-4fa8-9196-6c8b1b2a3da0@www.fastmail.com> <CAMrTa2H9Y5PcyvQvgBieB_3nxGf9xHwOE-zijAGSBuwE7T6PqA@mail.gmail.com>
 <CAMrTa2HKaUS0yioyOE1+LD1mDx8hS=zJ0NhhNPd+1Yj-AjR6Eg@mail.gmail.com> <2beca228-39ab-a2c6-41c2-136d88551205@processus.org>
In-Reply-To: <2beca228-39ab-a2c6-41c2-136d88551205@processus.org>
Date: Mon, 23 Aug 2021 16:23:10 +0200
Message-ID: <CANS-=pe7p=Gnp4tZZ+XaMmAHp8ffRbvZSPOs3SRqy16Hh9frVA@mail.gmail.com>
To: Pierre <pierre-php@processus.org>
Cc: Jordan LeDoux <jordan.ledoux@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004d438005ca3ac32e"
Subject: Re: [PHP-DEV] [RFC] User Defined Operator Overloads
From: kjarli@gmail.com (Lynn)

--0000000000004d438005ca3ac32e
Content-Type: text/plain; charset="UTF-8"

On Mon, Aug 23, 2021 at 4:03 PM Pierre <pierre-php@processus.org> wrote:

>
> Anyway, I always thought that __set, __get __call and __invoke should
> have been banned a long time ago.
>

Considering I use __invoke on a daily basis as it makes life so much easier
when you have single method (service) classes, I'm going to disagree on
this one. The other functions are also very useful tools to migrate legacy
code.

I agree that not being able to click through to operator overloading
methods is annoying, untraceable __toString is the worst. I do think that
this is something IDEs can handle, though not sure how reviewing will be
when diffs still hide the implementation.

--0000000000004d438005ca3ac32e--