On Wed, Oct 26, 2016 at 7:42 AM, David Lundgren <dlundg...@syberisle.net> wrote:
> Greetings,
>
> As suggested by several reviewers of a PR[1] I recently submitted, I'd
> like to get feedback on letting custom Iterators be used in the current,
> next, reset, and key functions. If this is something to move forward
> with, I'll need some help with the RFC process.
>
> Recent experiences trying to use these functions with a custom Iterator,
> and a bug[2], led me to try and fix this. BC will occur when an object
> implementing Iterator is passed to one of the functions, as the
> interface methods will be called, instead of returning the objects
> properties. The old behavior should be maintained for classes that do
> not implement Iterator.
>
> [1] https://github.com/php/php-src/pull/2176
> [2] https://bugs.php.net/bug.php?id=49369
>
> Thanks,
> Dave
> --
> David Lundgren
> dlundg...@syberisle.net
> 808.639.0365
> GPG: 0x26F54D7F
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php

I can't seem to recall specifics anymore but I do believe some people
would greatly prefer to remove the internal array pointer for
iteration and deprecate these functions. Maybe someone else can
remember more? Nikita and Bob, maybe?

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to