Hi Tim, On Apr 9, 2026, 10:39 AM, Tim Düsterhus <[email protected]> wrote: > 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.
Thanks for the feedback, I just fixed the RFC <https://wiki.php.net/rfc/const_object_property_write> rendering issues. Best regards, __ *Khaled Alam* On Thu, Apr 9, 2026 at 10:39 AM Tim Düsterhus <[email protected]> wrote: > 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 >
