Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126265
Message-ID: <D0813EB5-1F6B-4AB7-8A77-3A2899F947F1@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_11CB7A0F-A42F-4099-9DFE-E9FA63B93014"
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.113.1.2\))
Subject: Re: [PHP-DEV] RFC Karma Request
Date: Sun, 2 Feb 2025 12:28:16 +0300
In-Reply-To: <CAPyj-LCwQ3xPUhg29QQqzXuNRrLaGaJ2gFDbq8t92gbnJr7xbA@mail.gmail.com>
Cc: PHP internals <internals@lists.php.net>
To: Ilija Tovilo <tovilo.ilija@gmail.com>
References: <B7E344D6-A7CE-4E10-BA12-B329123CC30B@gmail.com>
 <CAPyj-LCwQ3xPUhg29QQqzXuNRrLaGaJ2gFDbq8t92gbnJr7xbA@mail.gmail.com>
From: xepozzd@gmail.com (Dmitry Derepko)


--Apple-Mail=_11CB7A0F-A42F-4099-9DFE-E9FA63B93014
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thank you, Ilija. I really appreciate it.

Could you please advise do I need to create RFC or it=E2=80=99s better =
do to it after solving technical issues?

If so, one common RFC or each for each operator: return, break, =
continue?

I=E2=80=99d also like to see all this problems by myself and I have a =
question. Is it possible to run php and add breakpoints somewhere at the =
parser and any other places? Is there an instruction how to profile it?  =
Thanks

----------

Best regards,
Dmitrii Derepko.
@xepozz



> On Feb 1, 2025, at 1:04=E2=80=AFAM, Ilija Tovilo =
<tovilo.ilija@gmail.com> wrote:
>=20
> Hi Dmitrii
>=20
> On Fri, Jan 31, 2025 at 3:10=E2=80=AFPM Dmitry Derepko =
<xepozzd@gmail.com> wrote:
>>=20
>> I=E2=80=99m looking for way to gain some Karma to create an RFC.
>> I=E2=80=99ve already made first implementation and shared it: =
https://github.com/php/php-src/pull/17647
>>=20
>> I can make 3 different RFC to discuss each change separately, let me =
know if it=E2=80=99s necessary.
>=20
> RFC karma was granted. Good luck!
>=20
> Note that I believe we should solve the technical issues mentioned on
> the PR before voting on this RFC. They are very much non-trivial to
> solve (I have tried multiple solutions over the years, all of which so
> far were complex or otherwise unsatisfactory). But I would be ready to
> investigate further, given that my long-standing RFC for match-blocks
> [1] is also affected, at least in an unrestricted form.
>=20
> Ilija
>=20
> [1] https://wiki.php.net/rfc/match_blocks


--Apple-Mail=_11CB7A0F-A42F-4099-9DFE-E9FA63B93014
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;">Thank you, =
Ilija. I really appreciate it.<br><br>Could you please advise do I need =
to create RFC or it=E2=80=99s better do to it after solving technical =
issues?<br><br>If so, one common RFC or each for each operator: return, =
break, continue?<br><br>I=E2=80=99d also like to see all this problems =
by myself and I have a question. Is it possible to run php and add =
breakpoints somewhere at the parser and any other places? Is there an =
instruction how to profile it? &nbsp;Thanks<br =
id=3D"lineBreakAtBeginningOfMessage"><div>
<div><br>----------<br><br>Best regards,<br>Dmitrii =
Derepko.<br>@xepozz<br><br><br></div>

</div>
<div><br><blockquote type=3D"cite"><div>On Feb 1, 2025, at 1:04=E2=80=AFAM=
, Ilija Tovilo &lt;tovilo.ilija@gmail.com&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div>Hi Dmitrii<br><br>On Fri, =
Jan 31, 2025 at 3:10=E2=80=AFPM Dmitry Derepko &lt;xepozzd@gmail.com&gt; =
wrote:<br><blockquote type=3D"cite"><br>I=E2=80=99m looking for way to =
gain some Karma to create an RFC.<br>I=E2=80=99ve already made first =
implementation and shared it: =
https://github.com/php/php-src/pull/17647<br><br>I can make 3 different =
RFC to discuss each change separately, let me know if it=E2=80=99s =
necessary.<br></blockquote><br>RFC karma was granted. Good =
luck!<br><br>Note that I believe we should solve the technical issues =
mentioned on<br>the PR before voting on this RFC. They are very much =
non-trivial to<br>solve (I have tried multiple solutions over the years, =
all of which so<br>far were complex or otherwise unsatisfactory). But I =
would be ready to<br>investigate further, given that my long-standing =
RFC for match-blocks<br>[1] is also affected, at least in an =
unrestricted form.<br><br>Ilija<br><br>[1] =
https://wiki.php.net/rfc/match_blocks<br></div></div></blockquote></div><b=
r></body></html>=

--Apple-Mail=_11CB7A0F-A42F-4099-9DFE-E9FA63B93014--