Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62129
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50280D37.10109@moonspot.net>
References: <CAF+90c_pRo6Xs2Cv9X-BN3mSnHi65gHHWzD8+yOnAPqgnWJm_w@mail.gmail.com>
	<50280D37.10109@moonspot.net>
Date: Mon, 13 Aug 2012 18:09:32 +0200
Message-ID: <CAF+90c_pG0sSE_uvtsdN6iXwtv=1SSO1pYH7Hy-hO9aWA=JdAw@mail.gmail.com>
To: Brian Moon <brian@moonspot.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [RFC] Generators
From: nikita.ppv@gmail.com (Nikita Popov)

On Sun, Aug 12, 2012 at 10:08 PM, Brian Moon <brian@moonspot.net> wrote:
> Also, not allowing rewinding is unintuitive for something that is an
> iterator in PHP. If I can foreach() it and I can call next() on it, I expect
> to be able to reset() it as well. IMO, you would need to issue a FATAL PHP
> error if that simply is not allowed. Or you have to have a second syntax for
> what to do in that case. At that point, you are implementing Iterator.

Currently I'm planning to implement the following behavior for rewind():

 * If before first yield: Resume to first yield (this priming behavior
is common to all the Iterator methods)
 * At first yield: No-op
 * After first yield: Recoverable fatal error

So this would allow you to call ->rewind() after creating the
generator, but will throw an error if you try to do so later.

Another thing that I'd like to do is drop the ->close() method. It
doesn't really make sense to explicitly close generators.

Any objects to those two things?

Nikita