Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96614
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain syberisle.net designates 96.126.116.40 as permitted sender)
To: internals@lists.php.net
Message-ID: <44244cfd-c8ad-e0a9-4e70-380a8a8c940c@syberisle.net>
Date: Wed, 26 Oct 2016 08:42:59 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0)
 Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Allow Iterator to be used with current, next, reset, key functions
From: dlundgren@syberisle.net (David Lundgren)

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
dlundgren@syberisle.net
808.639.0365
GPG: 0x26F54D7F