Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130593
Precedence: list
MIME-Version: 1.0
Date: Thu, 09 Apr 2026 10:39:21 +0200
To: Khaled Alam <khaledalam.net@gmail.com>
Cc: Ilija Tovilo <tovilo.ilija@gmail.com>, PHP internals
 <internals@lists.php.net>
Subject: Re: [PHP-DEV] [php-src] PR #20903: GH-10497 (const obj->prop write) -
 language change notes
In-Reply-To: <CAJS5taA-27Vj8xsQOt62urEcCWFgK5F2+71eb7P=txSX1q3-5A@mail.gmail.com>
References: <CAJS5taANCzu9W+mzEd0-nE0hh22Jbb170jK7n2yBHjh7yj-gdA@mail.gmail.com>
 <dcee998d-4727-46a2-ba3c-03e71863ef3e@bastelstu.be>
 <CAPyj-LBLqUu=_wYRSdmmk2vDtoQcuJNQ-K4y0yns_hj_t9_KWg@mail.gmail.com>
 <433cf40fdc4a5459b9b87e966f02a96f@bastelstu.be>
 <CAJS5taA-27Vj8xsQOt62urEcCWFgK5F2+71eb7P=txSX1q3-5A@mail.gmail.com>
Message-ID: <4764272e616126506cb878d48f4805cd@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2026-04-04 02:52, schrieb Khaled Alam:
> I'd like to bring attention back to this RFC, which has been updated to
> v0.2 based on prior feedback:
> 
> https://wiki.php.net/rfc/const_object_property_write

Thank you. The updated RFC makes sense to me and with the removal of the 
`FOO[123] = 'bar';` support I don't have any further technical concerns.

With regard to the RFC policy, I just added the necessary “Abstain” 
option to the vote.

I'm also noting some rendering issues in the RFC, particularly in the 
Proposal section, where the “bullet point list” does not render 
properly, due to the line-breaks in the markup. I'm also seeing that you 
try to use the markdown syntax for inline code. That doesn't work in the 
Wiki, since it doesn't speak markdown. When showcasing PHP code, I 
recommend using <php>isset()</php> tags (<php> XML tag). For 
non-PHP-Code ''BP_VAR_FUNC_ARG'' (two single-quotes works). You might 
want to clean-up both of these, it will make the RFC look much nicer and 
more approachable.

Please note that your RFC update is considered a major change, so it 
needs 14 days of “cooldown” for discussion, before the RFC can go to 
vote.

Best regards
Tim Düsterhus