Re: Re: NULL Coercion Consistency
| From: | Aleksander Machniak | Date: | Sat, 28 May 2022 06:25:00 +0000 |
| Subject: | Re: Re: NULL Coercion Consistency | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117812@lists.php.net to get a copy of this message | ||
On 28.05.2022 04:36, Craig Francis wrote:
On 8 Apr 2022, at 18:34, Craig Francis <craig@craigfrancis.co.uk> wrote:Don't give up. You have my Yes vote. Imo, the RFC: - fixes real upgrade problem (very important), - improves consistency in a better way than the solution introduced in 8.1. - does not change strict_types behavior Some people don't care with what arguments their functions are called with. As long as the value can be coerced to the expected type the function will do what it is supposed to do. Other people have strict_types. All people don't want to be forced to modify a working code. So, this is another "battle" between strict and non-strict camps. I'd like to see which is the majority these days. I hope that even some strict-code proponents can see this makes sense. -- Aleksander Machniak Kolab Groupware Developer [https://kolab.org] Roundcube Webmail Developer [https://roundcube.net] ---------------------------------------------------- PGP: 19359DC1 # Blog: https://kolabian.wordpress.comI've written a new draft RFC to address the NULL coercion problems: https://wiki.php.net/rfc/null_coercion_consistencyI give up.