Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122840
Precedence: bulk
MIME-Version: 1.0
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>
 <eb6d95ed-32f9-49e0-8af3-d74d05a01d2f@app.fastmail.com>
In-Reply-To: <eb6d95ed-32f9-49e0-8af3-d74d05a01d2f@app.fastmail.com>
Date: Mon, 1 Apr 2024 07:23:01 +0800
Message-ID: <CAKkgovR047QvEgL3MH1emSQkqKGBRLXn=dq9ga8Ke=7KVWae2g@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Invoke __callStatic when non-static public
 methods are called statically
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000002176550614fd2811"
From: daddyofsky@gmail.com (=?UTF-8?B?7ZWY64qY7JWE67aA7KeA?=)

--0000000000002176550614fd2811
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

2024=EB=85=84 4=EC=9B=94 1=EC=9D=BC (=EC=9B=94) =EC=98=A4=EC=A0=84 2:31, La=
rry Garfield <larry@garfieldtech.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:

> 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
> static-like manner is common *in Laravel*
> >
> > It might be correct to say that this is specific to Laravel. The
> > problem, however, is that Laravel is used so extensively that it cannot
> > be ignored.
>
> True, but as someone else noted, Laravel already has a workaround in plac=
e
> for this.  WordPress is orders of magnitude more popular than Laravel, bu=
t
> we don't generally design the language to work "the WordPress way," becau=
se
> 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
> > accepted, would create problems that did not previously exist. Yet, the
> > existence of `__callStatic` already allows for the issues you've
> > pointed out to occur. You can already write code like
> > `foo::bar()::baz()` with the current PHP. The possibility of more
> > problems arising could indeed be true. In that sense, I understand your
> > 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 another=
,
> and trust the feeling is mutual.  That you're interested in improving PHP
> is to your credit, and I thank you for that.
>
> However, that is separate from the proposal itself, which for reasons
> stated I think is not a good one.  That should not reflect on you
> personally in any way, and is explicitly not intended as such.  Certainly
> I've had enough of my proposals rejected around here. :-)
>
> --Larry Garfield
>

I understand.
I didn't assume my proposal would be accepted without question. I just
started because I hate doing nothing.

Daddyofsky

--0000000000002176550614fd2811
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">2024=EB=85=84 4=EC=9B=94 1=EC=9D=BC (=
=EC=9B=94) =EC=98=A4=EC=A0=84 2:31, Larry Garfield &lt;<a href=3D"mailto:la=
rry@garfieldtech.com">larry@garfieldtech.com</a>&gt;=EB=8B=98=EC=9D=B4 =EC=
=9E=91=EC=84=B1:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>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:<br>
<br>
&gt;&gt; It would be more accurate to say &quot;calling non-static methods =
in a static-like manner is common *in Laravel* <br>
&gt;<br>
&gt; It might be correct to say that this is specific to Laravel. The <br>
&gt; problem, however, is that Laravel is used so extensively that it canno=
t <br>
&gt; be ignored.<br>
<br>
True, but as someone else noted, Laravel already has a workaround in place =
for this.=C2=A0 WordPress is orders of magnitude more popular than Laravel,=
 but we don&#39;t generally design the language to work &quot;the WordPress=
 way,&quot; because that is well-recognized as a not-good way to work.<br>
<br>
Popularity matters, but quality matters more.<br>
<br>
&gt; There&#39;s a point of embarrassing me. It&#39;s as if my proposal, if=
 <br>
&gt; accepted, would create problems that did not previously exist. Yet, th=
e <br>
&gt; existence of `__callStatic` already allows for the issues you&#39;ve <=
br>
&gt; pointed out to occur. You can already write code like <br>
&gt; `foo::bar()::baz()` with the current PHP. The possibility of more <br>
&gt; problems arising could indeed be true. In that sense, I understand you=
r <br>
&gt; point.<br>
<br>
To be clear: I have no interest or desire to embarrass you personally.=C2=
=A0 I have never met you before so have no opinion about you one way or ano=
ther, and trust the feeling is mutual.=C2=A0 That you&#39;re interested in =
improving PHP is to your credit, and I thank you for that.<br>
<br>
However, that is separate from the proposal itself, which for reasons state=
d I think is not a good one.=C2=A0 That should not reflect on you personall=
y in any way, and is explicitly not intended as such.=C2=A0 Certainly I&#39=
;ve had enough of my proposals rejected around here. :-)<br>
<br>
--Larry Garfield<br></blockquote><div><br></div><div>I understand.<br>I did=
n&#39;t assume my proposal would be accepted without question. I just start=
ed because I hate doing nothing.<br><br></div><div>Daddyofsky<br></div><div=
>=C2=A0</div></div></div>

--0000000000002176550614fd2811--