Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126269
Message-ID: <878EED34-B28D-48FE-8EBE-5929841C12BD@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_077ED169-F7AC-45B4-96F7-21656C8908CC"
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.113.1.2\))
Subject: [PHP-DEV] Re: Discussion: making continue and break into an expression
Date: Sun, 2 Feb 2025 16:35:33 +0300
In-Reply-To: <CAPzBOBMh5DR9opccsXHaijBFYG7gk=gAOBpnHFRVHKh6+Mzh8A@mail.gmail.com>
Cc: internals <internals@lists.php.net>
To: Robert Landers <landers.robert@gmail.com>
References: <CAPzBOBMh5DR9opccsXHaijBFYG7gk=gAOBpnHFRVHKh6+Mzh8A@mail.gmail.com>
From: xepozzd@gmail.com (Dmitry Derepko)


--Apple-Mail=_077ED169-F7AC-45B4-96F7-21656C8908CC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Jan 25, 2024, at 12:16=E2=80=AFPM, Robert Landers =
<landers.robert@gmail.com> wrote:
>=20
> Hello internals,
>=20
> Now that throwing is an expression, it allows for some very concise
> programming. What are your thoughts on making a break/continue into an
> expression as well?


Hi!=20
I had similar idea to make `break`, `continue` and `return` be =
expressions instead of statements to simplify almost the same cases as =
Robert described above.

Grammar corrections in the PR. https://github.com/php/php-src/pull/17647=20=

Ilija pointed to memory leaking problems as well.

Thinking about Ilija memory leaking case:
new Foo + return 1

I think we may have a workaround here, by allowing all of these =
constructions only available at some specific points:
- <point> as the statement now
- $cond ? <point> : <point>;
- match ($v) { =E2=80=A6 =3D> <point> }

So it will deny such cases:
- operand OPERATOR <point> (1 + return; $cond && break; etc)

It may prevent memory leaking problems. Isn=E2=80=99t it?

I=E2=80=99m writing RFC: =
https://wiki.php.net/rfc/return_break_continue_expressions=20
I=E2=80=99ll start a new discussion when it will be ready for it.


----------

Best regards,
Dmitrii Derepko.
@xepozz


--Apple-Mail=_077ED169-F7AC-45B4-96F7-21656C8908CC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: =
after-white-space;"><div><div><div><br></div></div><div><blockquote =
type=3D"cite"><div>On Jan 25, 2024, at 12:16=E2=80=AFPM, Robert Landers =
&lt;landers.robert@gmail.com&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div>Hello =
internals,<br><br>Now that throwing is an expression, it allows for some =
very concise<br>programming. What are your thoughts on making a =
break/continue into an<br>expression as =
well?<br></div></div></blockquote><br></div><div><br></div><div>Hi!&nbsp;<=
div>I had similar idea to make `break`, `continue` and `return` be =
expressions instead of statements to simplify almost the same cases as =
Robert described above.</div><div><br></div><div>Grammar corrections in =
the PR.&nbsp;<a =
href=3D"https://github.com/php/php-src/pull/17647">https://github.com/php/=
php-src/pull/17647</a>&nbsp;</div><div>Ilija pointed to memory leaking =
problems as well.</div><div><br></div><div>Thinking about Ilija memory =
leaking case:</div><div>new Foo + return 1</div><div><br></div><div>I =
think we may have a workaround here, by allowing all of these =
constructions only available at some specific points:</div><div>- =
&lt;point&gt; as the statement now</div><div>- $cond ? &lt;point&gt; : =
&lt;point&gt;;</div><div>- match ($v) { =E2=80=A6 =3D&gt; &lt;point&gt; =
}</div><div><br></div><div>So it will deny such cases:</div><div>- =
operand OPERATOR &lt;point&gt; (1 + return; $cond &amp;&amp; break; =
etc)</div><div><br></div><div>It may prevent memory leaking problems. =
Isn=E2=80=99t it?</div><div><br></div><div>I=E2=80=99m writing =
RFC:&nbsp;<a =
href=3D"https://wiki.php.net/rfc/return_break_continue_expressions">https:=
//wiki.php.net/rfc/return_break_continue_expressions</a>&nbsp;</div><div>I=
=E2=80=99ll start a new discussion when it will be ready for =
it.</div><div><br =
id=3D"lineBreakAtBeginningOfMessage"><div><div><br>----------<br><br>Best =
regards,<br>Dmitrii =
Derepko.<br>@xepozz<br></div></div></div></div><br></div></body></html>=

--Apple-Mail=_077ED169-F7AC-45B4-96F7-21656C8908CC--