Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117723
Message-ID: <5E4825B2-1F01-4783-B95F-3ECC6C40C3C2@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_9241014C-19ED-4C93-B7A3-EB4E3CCA5716"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Thu, 12 May 2022 23:30:26 +0200
In-Reply-To: <0d42a208-fc73-4277-a975-6f91c24648c1@www.fastmail.com>
Cc: php internals <internals@lists.php.net>
To: Larry Garfield <larry@garfieldtech.com>
References: <627D3BCF.7020903@adviesenzo.nl>
 <0d42a208-fc73-4277-a975-6f91c24648c1@www.fastmail.com>
Subject: Re: [PHP-DEV] [Discussion] Expand deprecation notice scope for
 partially supported callables
From: claude.pache@gmail.com (Claude Pache)

--Apple-Mail=_9241014C-19ED-4C93-B7A3-EB4E3CCA5716
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> Le 12 mai 2022 =C3=A0 23:11, Larry Garfield <larry@garfieldtech.com> a =
=C3=A9crit :
>=20
> For the `callable` type declaration, I'm not opposed but is it =
redundant with the existing deprecation?  When would you pass a callable =
to something and not end up calling it anyway, which would trigger the =
existing deprecation?  (Meaning in practice you'd always get 2 =
deprecations, which are not necessarily better than one.)


Although such a callable is probably intended to be called at some =
point, it is not necessarily called immediately, and it may be easier to =
track the source of it when you trigger the deprecation earlier. =
Example:

```php
public function registerErrorHandler(callable $onerror) {
    $this->onError[] =3D $onerror;
}
```

(Of course, this argument also holds for `is_callable()`.)

=E2=80=94Claude=

--Apple-Mail=_9241014C-19ED-4C93-B7A3-EB4E3CCA5716--