> I also think it is a good thing to clean up the ways to work with > arrays or iterable but we have to be very careful how we do it. I am > not sure an actual deprecation is a good thing in 7.x without breaking > any kind of tests out there. Indeed it will not break code but it is > rather bad to break tests and it is a very annoying thing to do while > trying to be good at using the latest PHP version.
I understand the concern here but getting out deprecation notices out early would be more important in my opinion. Additionally when we decided to make PHP 7 our next release we had already released 5.6. I pushed for a 5.7 to allow for deprecation notices as well as more time to develop features for 7.0 but that's not the route we took. I point this out to show that waiting for the last 7.x release is not prudent. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
