On Thu, Aug 6, 2026, at 10:48 AM, Jorg Sowa wrote: > Thank you both for the opinions. I think it will be reasonable to not > rush for PHP 8.6. I found few nuances that I would like to consider > properly. I will finish it after feature freeze. > >> I do agree here there's a bit too much punctuation. Perhaps something >> similar to what Python does (according to the posted link)? > >> Call to undefined function defined(). Did you mean: define? > > I have hard time choosing best option. Python and Ruby don't have file > and line number at the end of error message and question mark looks > good in such setup. I don't want change the error structure to put the > suggestion part at the end of error message. But otherwise in all cases > I think of, it looks ugly. > > Kind regards, > Jorg
I'm in favor of this improvement, but I agree it's best to not rush it. If it doesn't happen until 2027, that's OK. I also don't have especially strong opinions on the precise wording, so will largely leave that to those who do care. I don't think an RFC is needed here, but if we decide to have one, I'd recommend it be an abstract "we should use this pattern for error messages" type RFC, not one that deals with specific examples. Keep it flexible. --Larry Garfield
