Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115920
MIME-Version: 1.0
References: <CAF+90c-taw2SQFvTBTMbOO8PPdiqYC4TUoBYMvVZ82DoWyXshQ@mail.gmail.com>
 <20210902170608.07b09817@mcmic-probook.opensides.be>
In-Reply-To: <20210902170608.07b09817@mcmic-probook.opensides.be>
Date: Thu, 2 Sep 2021 17:45:24 +0200
Message-ID: <CAF+90c9aaiyJPQVO+T-9fA4J4uBTsWrkXyk4A8y6aK_apzre8Q@mail.gmail.com>
To: =?UTF-8?Q?C=C3=B4me_Chilliet?= <come.chilliet@fusiondirectory.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003ddf3d05cb0513f8"
Subject: Re: [PHP-DEV] [RFC] Deprecate partially supported callables
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000003ddf3d05cb0513f8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 2, 2021 at 5:06 PM C=C3=B4me Chilliet <
come.chilliet@fusiondirectory.org> wrote:

> Le Thu, 2 Sep 2021 16:32:32 +0200,
> Nikita Popov <nikita.ppv@gmail.com> a =C3=A9crit :
>
> > Hi internals,
> >
> > Currently, there are some callables that are accepted by the "callable"
> > type, but which cannot be used with $callable() syntax. This RFC propos=
es
> > to deprecate support for such "callables":
> >
> > https://wiki.php.net/rfc/deprecate_partially_supported_callables
>
> It took me some time to understand that this was not a proposal to remove
>  support for all array/string representation of callables.
> This should be made clearer if possible, maybe even list the callable kin=
ds
>  which will not be deprecated.
>

Yeah, I definitely have no intention of deprecating string/array callables
in general. If something works in $callable(), then it's going to continue
working. Added the following note:

> Normal "function", "Foo::method", ["Foo", "method"] and [new Foo,
"method"] style callables are unaffected by this change.

Regards,
Nikita

--0000000000003ddf3d05cb0513f8--