Re: Re: Decoding HTML and the Ambiguous Ampersand
| From: | Gina P. Banyard | Date: | Sat, 17 Aug 2024 22:39:55 +0000 |
| Subject: | Re: Re: Decoding HTML and the Ambiguous Ampersand | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-125036@lists.php.net to get a copy of this message | ||
On Friday, 16 August 2024 at 02:59, Dennis Snell <dennis.snell@automattic.com> wrote:
> [...]
>
> I have submitted an RFC draft for including the proposed feature from this issue. Thanks to
> everyone who helped me in this process. It’s my first RFC, so I apologize in advance for any
> mistakes I’ve made in the process.
>
> https://wiki.php.net/rfc/decode_html
>
> This is proposed for a future PHP version after 8.4.
I think the general idea is sensible.
Only focusing on UTF-8 is also a good design decision.
It took me a second to figure out what the $context parameters purpose was as you introduce the
constant later in the RFC.
However, I will echo another message in that this should be an enum because it is a new API.
Forcing the user to specify the context in which this function is called also seems like a good
idea.
Best regards,
Gina P. Banyard