>> >> There has been some debate about whether to make “PHP 5.7". I have >> made a very simple RFC. It proposes a final minor version of PHP 5, PHP >> 5.7, >> to be released at the same time as PHP 7, with no new features whatsoever. >> >> >> > I am wondering why we need that? no new features.... >> > >> > I think we can extend 5.6 release cycle to avoid that.. >> >> Extending the PHP 5.6 release cycle doesn't give an opportunity to raise >> different E_STRICT and E_DEPRECATED messages in preparation for PHP 7.0. >> This may or may not be something you value, but it's something I >> personally >> value. > > I don't see why we'd need new E_STRICT's, but what stops us from adding > E_DEPRECATED to 5.6.x?
Changing which errors and warnings are emitted in a patch release will likely fill up some unsuspecting user's HDD, and for people writing their own error handlers it may also mess them up. I'd much rather see the change happen in a minor version. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
