Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99696
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 74.125.82.43 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <CAH0Uv3Gx_OGBA4zwzE97mbK_VtwBtRCX3yn9JNv81VWtQbCYtA@mail.gmail.com>
References: <CAH0Uv3Gx_OGBA4zwzE97mbK_VtwBtRCX3yn9JNv81VWtQbCYtA@mail.gmail.com>
Date: Sun, 2 Jul 2017 22:15:30 -0400
Message-ID: <CAESVnVoQ-+mbUiXAUO1tsRzAqSGJnOnxba9qe=HAU-kqCyYTng@mail.gmail.com>
To: Andreas Hennings <andreas@dqxtech.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] "Reader" as alternative to Iterator
From: pollita@php.net (Sara Golemon)

On Sat, Jul 1, 2017 at 1:38 PM, Andreas Hennings <andreas@dqxtech.net> wrote:
> Hello internals,
> (this is my first email to this list, hopefully I'm doing ok.)
>
Welcome to php-internals!

> Establish a new interface in core, "Reader" or "ReaderInterface" (*).
> This interface has only one method, "->read()".
> The existing interface Iterator will remain unchanged.
>
Rather than introduce a new kind of iteration mechanism, how about
just creating a library in userspace which provides a proxy interface:

class Reader implements Iterator {
  protected $it;
  public function __construct(iterable $it) { $this->it = $it; }
  public function current/key/next/rewind/valid() {
$this->it->current/key/next/rewind/valid(); }
  public function read() { /* What a reader should be */ }
}

Then you can use any already extant iterable via:  $reader = new
Reader($iterable);
This could live in a composer/packagist library and work on already
released versions of PHP.
Or is there something I'm missing?

-Sara