Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99714
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain dqxtech.net from 209.85.223.181 cause and error)
MIME-Version: 1.0
In-Reply-To: <1499095625.19635.52.camel@schlueters.de>
References: <CAH0Uv3Gx_OGBA4zwzE97mbK_VtwBtRCX3yn9JNv81VWtQbCYtA@mail.gmail.com>
 <1499095625.19635.52.camel@schlueters.de>
Date: Mon, 3 Jul 2017 17:58:16 +0200
Message-ID: <CAH0Uv3HsN6=QLufUBWNRG1hu4Fv4J41qQqXkDSr6hye_OGM-Ew@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] "Reader" as alternative to Iterator
From: andreas@dqxtech.net (Andreas Hennings)

On Mon, Jul 3, 2017 at 5:27 PM, Johannes Schl=C3=BCter
<johannes@schlueters.de> wrote:
>
> Wouldn't SPL's NoRewindIterator be enough?
>
> $nit =3D new NoRewindIterator($it);
>
> foreach ($nit as $row) {
>  break;
> }
> foreach ($nit as $row) {
>   // continues same iteration
> }

I had not noticed this class :)

My motivation was to be able to use iterators and readers interchangeably.
Readers are easier to implement as classes.
Iterators have the benefit of the generator syntax.
The idea is to have a library where some stuff is implemented as
reader classes, and some other things are implemented as iterator
classes.

Then for the actual operational code, I need to choose to use either
iterator syntax or reader syntax. So either I need adapters for all
iterators, or I need adapters for all readers.

The NoRewindIterator would make it more viable to work with iterator
syntax on operation level.
So yes, it is a helpful hint. Not sure if it makes me fully happy.