Re: Proposal to deprecate create_function()

From: Date: Fri, 18 Oct 2013 16:03:39 +0000
Subject: Re: Proposal to deprecate create_function()
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message 
On 18/10/2013 15:51, Ferenc Kovacs wrote:

shouldn't really happen if you strictly follow the "new" release process rfc was accepted: https://wiki.php.net/rfc/releaseprocess , unfortunatelly it seems that there are some cases, when this can happen (some bug fixes, but the biggest offender was dropping deprecated features for 5.4.0 which were already removed in the 6.0 branch), but if you check out http://hu1.php.net/manual/en/migration55.incompatible.php you can see that the actual intentional BC breaks was really small, the only non bugfix BC break was removing the php logo urls, which was never meant to be a public api, but to be used by phpinfo().


Ah, I see. I guess it was the slew of changes in 5.3 and 5.4 which made it seem like this wasn't the case, because they would collectively have been 6.0. So the aim is that a script made to work on PHP 5.4 will now be guaranteed to run on any version <6, although some required modules might have moved to PECL?

As a user, it is certainly not obvious that features discussed as being removed "soon" will only actually disappear once there is a 6.0, because there doesn't seem to be any reason to expect PHP 6 to be "soon". Unless a release within the next few years is numbered 6.0 (or something else 
5) simply to clean up the deprecated functionality, without actually including major changes like the Unicode string concept.


-- 
Rowan Collins
[IMSoP]

Thread (33 messages)

« previous php.internals (#69689) next »