Re: Suggest similar names for undefined function/method/class errors

From: Date: Tue, 04 Aug 2026 07:55:27 +0000
Subject: Re: Suggest similar names for undefined function/method/class errors
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-132167@lists.php.net to get a copy of this message
Hello Jorg, On Tue, Aug 4, 2026, at 00:37, Jorg Sowa wrote: > “did you mean …?” suggestions to errors for undefined functions. While it does not change > language semantics, it changes error messages and introduces additional checks on error paths, so I > would like to confirm whether consensus on the PR is sufficient or an RFC is expected. > Thanks, this is great. According to PHP Policy RFC: Exempt input type and value validation from BC Break policy <https://wiki.php.net/rfc/policy-exempt-type-value-error-bc-policy>, rephrasing error messages is not subject to the backwards compatibility break policy. I think the amount of punctuation at the end is a bit much. Perhaps it would be clearer (although less strictly correct) to say "(did you mean func?)" instead of "(did you mean func()?)". But either way I am in favor of this. Regards, Sjoerd Langkemper

« previous php.internals (#132167) next »