Re: Allow Iterator to be used with current, next, reset, key functions
| From: | Rowan Collins | Date: | Sun, 30 Oct 2016 17:06:08 +0000 |
| Subject: | Re: Allow Iterator to be used with current, next, reset, key functions | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-96656@lists.php.net to get a copy of this message | ||
On 30/10/2016 04:31, Pierre Joye wrote:
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 don't follow this logic at all: isn't the whole point of deprecation notices to make people notice them? If people run tests with E_DEPRECATED active, it's presumably because they want those tests to tell them if they're using something deprecated; if people don't want the deprecation notices to break their tests, they can configure their test runner to ignore them. So who exactly is helped by not including those notices? Regards, -- Rowan Collins [IMSoP]