On 23-3-2022 14:46, Rowan Tommins wrote:
On 20/02/2022 18:55, Rowan Tommins wrote:
I would like to open discussion on an RFC to deprecate and later
remove the functions utf8_encode() and utf8_decode()
https://wiki.php.net/rfc/remove_utf8_decode_and_utf8_encode
Final chance for feedback
On Wed, Mar 23, 2022 at 4:10 PM Larry Garfield
wrote:
> On Wed, Mar 23, 2022, at 1:54 PM, Mark Niebergall wrote:
> > Hello All,
> >
> > In June 2020, Benas Seliuginas emailed this list (
> > https://externals.io/message/110755#110755) to gauge interest in typed
> > constants. An RFC
On Wed, Mar 23, 2022, at 1:54 PM, Mark Niebergall wrote:
> Hello All,
>
> In June 2020, Benas Seliuginas emailed this list (
> https://externals.io/message/110755#110755) to gauge interest in typed
> constants. An RFC (https://wiki.php.net/rfc/typed_class_constants) was
> started and had an
Hello All,
In June 2020, Benas Seliuginas emailed this list (
https://externals.io/message/110755#110755) to gauge interest in typed
constants. An RFC (https://wiki.php.net/rfc/typed_class_constants) was
started and had an accompanying PR (https://github.com/php/php-src/pull/5815).
At the time,
As someone who has spent a _lot_ of time on IRC and StackOverflow answering
encoding questions over the last 10 years or so I am 100% behind this
change, even though I'm not able to vote for it.
Thank you for putting this RFC forward.
On Wed, Mar 23, 2022 at 6:47 AM Rowan Tommins
wrote:
> On
On Tue, Mar 22, 2022 at 7:21 PM Larry Garfield
wrote:
> Are we talking about *arbitrary* user-space operator overloading?
> Because a very specific, non-arbitrary, well-designed operator
> overloading RFC was just rejected.
>
Yup. This was pointed out to me in r11, I guess I must have missed
On 20/02/2022 18:55, Rowan Tommins wrote:
I would like to open discussion on an RFC to deprecate and later
remove the functions utf8_encode() and utf8_decode()
https://wiki.php.net/rfc/remove_utf8_decode_and_utf8_encode
Final chance for feedback on this RFC, as revised, before I put it to
