On Wed, Aug 9, 2017 at 5:23 PM, Christoph M. Becker <cmbecke...@gmx.de> wrote:
> On 08.08.2017 at 18:07, Nikita Popov wrote: > > > On Tue, Aug 8, 2017 at 5:43 PM, Christoph M. Becker <cmbecke...@gmx.de> > > wrote: > > > >> On 29.01.2017 at 16:52, Nikita Popov wrote: > >> > >>> On Sun, Jan 15, 2017 at 3:27 PM, Nikita Popov <nikita....@gmail.com> > >> wrote: > >>> > >>>> I've started the vote on https://wiki.php.net/rfc/ > deprecations_php_7_2. > >>>> All votes are 2/3 majority and end on 29-01-2017. > >>> > >>> Voting has been closed, all of the proposals in this RFC have been > >> accepted > >>> within 2/3 majority. > >> > >> What's the status here? Have all deprecations been implemented? The > >> RFC is still listed in the "Pending Implementation" section ( > >> <https://wiki.php.net/rfc#pending_implementation>). > > > > Apart from the last item everything is implemented. > > Thanks, Nikita. > > I assume that the $errcontext parameter of error handlers will not be > deprecated in PHP 7.2, but a later version. Would it make sense to > already document that the parameter shouldn't be used anymore (aka. soft > deprecation)? > I'm not sure on this one. I think it might actually be preferable to keep this as a documentation-only deprecation (and then directly remove it in PHP 8). I'm not really happy with the proposed action from the RFC (even though I suggested it myself), both in terms of behavior and implementation complexity. There's a number of fun edge-cases there, like a __call() method being used as error handler -- in that case the formal number of parameters is 2, but more might actually be used and we have no way to know. I don't even know what's supposed to happen in that case under the RFC. Nikita
