Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124523
Precedence: bulk
MIME-Version: 1.0
References: <66984FD0.5090805@adviesenzo.nl> <AM8P250MB0170FFCA0014FB9EC272DB4FE2AC2@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <c9736385-94b7-4064-911f-e5fc1df7e2bd@gmx.de> <AM8P250MB0170B4C59B4313A565CD029AE2AC2@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <6699F817.8070806@adviesenzo.nl> <9571bb82-9873-4319-9bd1-0361748335be@bastelstu.be>
 <669BDB00.70507@adviesenzo.nl> <fa7db246-1577-43b7-a117-c18a73140091@bastelstu.be>
 <669BE870.2050908@adviesenzo.nl> <b7b47e7a-fc20-4774-bc49-fff271386504@bastelstu.be>
In-Reply-To: <b7b47e7a-fc20-4774-bc49-fff271386504@bastelstu.be>
Date: Sat, 20 Jul 2024 15:14:32 -0300
Message-ID: <CADK1yXK4bapqAWLZLNk--Fvo87AOv2qbSM1mTn23gU1JSMcL_g@mail.gmail.com>
Subject: Re: [PHP-DEV] Request for opinions: bug vs feature - change
 intokenization of yield from
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: Juliette Reinders Folmer <php-internals_nospam@adviesenzo.nl>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000c67b0f061db1cacb"
From: deleugyn@gmail.com (Deleu)

--000000000000c67b0f061db1cacb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Jul 20, 2024 at 1:53=E2=80=AFPM Tim D=C3=BCsterhus <tim@bastelstu.b=
e> wrote:

> Hi
>
> On 7/20/24 18:40, Juliette Reinders Folmer wrote:
> > Tim, you're making my point for me. This is *exactly* why the current
> > change should be reverted.
>
> I am not sure how you read "PHP users have no idea what a token is" as
> an argument in favor of reverting the change, because reverting the
> change means that completely reasonable code suddenly stops working with
> a parser error in a patch version and PHP users will rightfully come to
> PHP's issue tracker to complain.
>

Is there any evidence that PHP users are relying on code that:

- Was released just 7 months ago
- Was not documented
- Nobody knew about it until very recently

And furthermore, why should undocumented, unintentional, unapproved change
to PHP be supported? Even if a handful of folks come to PHP's issue tracker
to complain, the answer is plain and simple: that behavior was not approved
by PHP's RFC process, which is the only way to get a behavior change
introduced into the language. Realistically, it's highly questionable that
such hypothetical users would even show up.


--=20
Marco Deleu

--000000000000c67b0f061db1cacb
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">On Sat, Jul 20, 2024 at 1:53=E2=80=AF=
PM Tim D=C3=BCsterhus &lt;<a href=3D"mailto:tim@bastelstu.be">tim@bastelstu=
.be</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">Hi<br>
<br>
On 7/20/24 18:40, Juliette Reinders Folmer wrote:<br>
&gt; Tim, you&#39;re making my point for me. This is *exactly* why the curr=
ent<br>
&gt; change should be reverted.<br>
<br>
I am not sure how you read &quot;PHP users have no idea what a token is&quo=
t; as <br>
an argument in favor of reverting the change, because reverting the <br>
change means that completely reasonable code suddenly stops working with <b=
r>
a parser error in a patch version and PHP users will rightfully come to <br=
>
PHP&#39;s issue tracker to complain.<br></blockquote><div><br></div><div>Is=
 there any evidence that PHP users are relying on code that:</div><div><br>=
</div><div>- Was released just 7 months ago</div><div>- Was not documented<=
/div><div>- Nobody knew about it until very recently</div><div><br></div><d=
iv>And furthermore, why should undocumented, unintentional, unapproved chan=
ge to PHP be supported? Even if a handful of folks come to PHP&#39;s=C2=A0i=
ssue tracker to complain, the answer is plain and simple: that behavior was=
 not approved by PHP&#39;s RFC process, which is the only way to get a beha=
vior change introduced into the language. Realistically, it&#39;s highly qu=
estionable that such hypothetical users would even show up.</div></div><br =
clear=3D"all"><div><br></div><span class=3D"gmail_signature_prefix">-- </sp=
an><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div dir=
=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr=
"><div dir=3D"ltr">Marco Deleu</div></div></div></div></div></div></div></d=
iv></div>

--000000000000c67b0f061db1cacb--