Re: NULL Coercion Consistency

On 8 Apr 2022, at 18:34, Craig Francis <craig@craigfrancis.co.uk> wrote: > I've written a new draft RFC to address the NULL coercion problems: > https://wiki.php.net/rfc/null_coercion_consistency I give up. I'm clearly not clever enough to understand what the benefits are for breaking NULL coercion... considering NULL has been coerced for internal functions since forever, and continues to work in other contexts. If anyone wants to work on a solution to the problem, feel free to either edit my RFC, or create your own RFC. I believe my RFC documents every position put forward, and includes all of details I think are relevant. I fear a vote now will only result in rejection; and once people put their names down for a certain position, they will never change their mind. That said, if someone did continue, and got their RFC accepted, I should be able to organise some funding for the implementation. For some background, I paid for the is_literal() implementation before that RFC vote, as that patch is useful irrespective of the result (it's being used in a few projects now, and works incredibly well; thanks again to Joe Watkins for writing, and Máté Kocsis for testing). In this case, two of my clients are considering the cost of modifying their code (by adding a load of ?? '' everywhere), and they would rather avoid that (time consuming, and makes their code more complicated). I suggested putting aside a budget to either do that modification, or fund the implementation if my RFC was to pass. I'm not sure how big or complicated the task would be, but I noted the R11 suggested day rate of $500 (~£390), and the implementation could take a few weeks. If anyone does want to email me about this, I won't respond until at least June 6th. Craig