Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122839
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-333-gbfea15422e-fm-20240327.001-gbfea1542
Precedence: bulk
MIME-Version: 1.0
Message-ID: <eb6d95ed-32f9-49e0-8af3-d74d05a01d2f@app.fastmail.com>
In-Reply-To: 
 <CAKkgovQPSdcusi=hs-mpfitnHHo7B0Xpqg7j29xqLvw0SX5T9A@mail.gmail.com>
References: 
 <CAKkgovQcibHLQibK44wtcEbi-oKVQ5ifCiZPgN8SR2RCg5yMGQ@mail.gmail.com>
 <bbbb6db9-f62b-4b2f-aa37-4d7193b96b09@app.fastmail.com>
 <CAKkgovSgY9-XXKjfQ2_nGoHEcnBMsG3zODwqHdMzW52s0o9tBw@mail.gmail.com>
 <a1041fae-d72d-4b46-a216-580dc3a9062a@app.fastmail.com>
 <CAKkgovQPSdcusi=hs-mpfitnHHo7B0Xpqg7j29xqLvw0SX5T9A@mail.gmail.com>
Date: Sun, 31 Mar 2024 12:17:42 -0500
To: "php internals" <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] Invoke __callStatic when non-static public methods are
 called statically
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: larry@garfieldtech.com ("Larry Garfield")

On Fri, Mar 29, 2024, at 6:12 PM, =ED=95=98=EB=8A=98=EC=95=84=EB=B6=80=EC=
=A7=80 wrote:

>> It would be more accurate to say "calling non-static methods in a sta=
tic-like manner is common *in Laravel*=20
>
> It might be correct to say that this is specific to Laravel. The=20
> problem, however, is that Laravel is used so extensively that it canno=
t=20
> be ignored.

True, but as someone else noted, Laravel already has a workaround in pla=
ce for this.  WordPress is orders of magnitude more popular than Laravel=
, but we don't generally design the language to work "the WordPress way,=
" because that is well-recognized as a not-good way to work.

Popularity matters, but quality matters more.

> There's a point of embarrassing me. It's as if my proposal, if=20
> accepted, would create problems that did not previously exist. Yet, th=
e=20
> existence of `__callStatic` already allows for the issues you've=20
> pointed out to occur. You can already write code like=20
> `foo::bar()::baz()` with the current PHP. The possibility of more=20
> problems arising could indeed be true. In that sense, I understand you=
r=20
> point.

To be clear: I have no interest or desire to embarrass you personally.  =
I have never met you before so have no opinion about you one way or anot=
her, and trust the feeling is mutual.  That you're interested in improvi=
ng PHP is to your credit, and I thank you for that.

However, that is separate from the proposal itself, which for reasons st=
ated I think is not a good one.  That should not reflect on you personal=
ly in any way, and is explicitly not intended as such.  Certainly I've h=
ad enough of my proposals rejected around here. :-)

--Larry Garfield