On Fri, Nov 18, 2016 at 6:45 PM, Christoph M. Becker <cmbecke...@gmx.de> wrote:
> On 18.11.2016 at 15:55, Nikita Popov wrote: > > Hi internals! > > > > I've submitted this RFC for PHP 7.1 previously, but didn't follow through > > due to time constraints. Now I'd like to propose an extended version for > > PHP 7.2 and vote on it sooner rather than later to avoid a repeat > > performance. > > > > https://wiki.php.net/rfc/deprecations_php_7_2 > > > > The RFC combines a number of deprecation and removal proposals. Each one > > will get a separate 2/3 majority vote. The RFC overlaps with some > recently > > discussed topics (each, binary strings) -- I'm fine with dropping these > if > > someone has a more specific RFC. > > > > I expect some of these are no-brainers, while others are more > controversial > > -- please share your specific concerns. > > Thanks, Nikita! I'm generally in favor of such clean up. > > The only exception would be features which have only been available as > of PHP 7, currently only assertion expressions. Deprecating assertion > strings as of PHP 7.2 would make it hard to provide PHP 5.6 and PHP 7.2 > compatible code, even though 7.2 GA is supposed to be released in > December 2017, whereas there'll be security support for 5.6 until end of > 2018[1]. > > [1] <http://php.net/supported-versions.php> > This is a reasonable concern. My opinion on assert() and PHP 5 vs PHP 7 is basically this: You can use assert() the same way in PHP 5 as you do in PHP 7. Assertion expressions *are* supported in PHP 5. The only difference is that it's not zero-cost and error reporting is slightly worse. And well, PHP 5 being slower than PHP 7 is kinda the case whether you use assertions or not. If you use PHP 5, performance is clearly your primary concern. Thanks, Nikita
