Re: Deprecated partially supported callables: should is_callable() throw a deprecation notice ?

On Mon, May 2, 2022 at 1:57 PM Alexandru Pătrănescu <drealecs@gmail.com> wrote: > On Mon, May 2, 2022 at 2:15 PM Guilliam Xavier <guilliam.xavier@gmail.com> wrote: >> I too would rather have "extra" deprecation notices in 8.2 than >> *sudden errors / silent behavior changes* in 9.0 (for the callable >> type declaration / the is_callable() function)... > > The point is that this is not an usual deprecation, something that will change to an error in > the future. > In the end, it's just a change in behavior with no error before or after. It does not fit > the "deprecation". This has already been said earlier, and answered: On Wed, Apr 20, 2022 at 12:22 AM Claude Pache <claude.pache@gmail.com> wrote: > > Le 19 avr. 2022 à 20:20, Andreas Hennings <andreas@dqxtech.net> a écrit : > > A deprecation warning on is_callable() would imply that in a future > > version of PHP that call will be illegal. > > No, in the case of is_callable(), the deprecation warning will > imply that, in a future version of PHP, the behaviour will change. There are precedents of > deprecation warning for changing behaviour: https://3v4l.org/Iqo4N Regards, -- Guilliam Xavier