Re: Soft-reserve "void" class name

From: Date: Tue, 19 May 2015 16:21:58 +0000
Subject: Re: Soft-reserve "void" class name
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-86309@lists.php.net to get a copy of this message
On Tue, May 19, 2015 at 10:16 AM, Levi Morrison <levim@php.net> wrote: > I strongly disagree with this action. These types required an RFC; why > should this be different? Also note that neither of the reserve > typename RFC were unanimous. > > Furthermore, we are past the RFC stage. We are *supposed to already > have an alpha* by now and we are proposing new changes?. Please stick > to our established rules and release timetables as much as possible, > thank you. On a related note it is unclear what BC breaks are exactly allowed in minor releases. Adding new reserved types is a BC break, but it was done in PHP 5.4 with callable. We should solidify what we do and do not allow in minor releases for the PHP 7 release series.

« previous php.internals (#86309) next »