Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62145
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain yahoo.de from 77.238.189.58 cause and error)
DomainKey-Status: good
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=FrQTabJld8bibqnIIge7K03uQ/4w92S7+V57h5Kc0JXqDL3bYkC9heiYG1sbI5awyaLIGjMLZE+hGkfW1P+MY0+waFoWrDtcSbNod4Ir0TipMYLLoiZMVCV6GQkgCZpv0X17MU8VcPc3pWgm78qe2r+ZMpRl7arH3OJfEkf4JuU=;
References: <CAF+90c_pRo6Xs2Cv9X-BN3mSnHi65gHHWzD8+yOnAPqgnWJm_w@mail.gmail.com> <50280D37.10109@moonspot.net> <CAF+90c_pG0sSE_uvtsdN6iXwtv=1SSO1pYH7Hy-hO9aWA=JdAw@mail.gmail.com>
Message-ID: <1344958783.95557.YahooMailNeo@web133003.mail.ir2.yahoo.com>
Date: Tue, 14 Aug 2012 16:39:43 +0100 (BST)
Reply-To: hakre <hanskrentel@yahoo.de>
To: Nikita Popov <nikita.ppv@gmail.com>,
  "brian@moonspot.net" <brian@moonspot.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
In-Reply-To: <CAF+90c_pG0sSE_uvtsdN6iXwtv=1SSO1pYH7Hy-hO9aWA=JdAw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Generators
From: hanskrentel@yahoo.de (hakre)

If I may chime in, not all iterators support rewind, at least not as outlin=
ed.=0A=0AThere exists also the NoRewindIterator which you can just use to d=
ecorate an iterator out of a generator to not make it do a fatal.=0A=0AHowe=
ver as far as a generator is concerned, it probably should just behave like=
 NoRewindIterator already so not give any errors on rewind. Because you can=
 not rewind what you can not rewind. No need to error, no need to do someth=
ing. The function is just there because of the interface, but it must not d=
o anything.=0A=0AIf different behavior is needed it could be decorated, but=
 right now I can not imagine why rewind would be called (apart from using i=
n foreach() for the first time which implies a rewind and that one is alrea=
dy like I suggest.)=0A=0A=0AMy 2 cents.=0A=0A-- hakre=0A=0A=0A=0A----- Ursp=
r=FCngliche Message -----=0A> Von: Nikita Popov <nikita.ppv@gmail.com>=0A> =
An: Brian Moon <brian@moonspot.net>=0A> CC: PHP internals <internals@lists.=
php.net>=0A> Gesendet: 18:09 Montag, 13.August 2012=0A> Betreff: Re: [PHP-D=
EV] [RFC] Generators=0A> =0A> On Sun, Aug 12, 2012 at 10:08 PM, Brian Moon =
<brian@moonspot.net> wrote:=0A>>  Also, not allowing rewinding is unintuiti=
ve for something that is an=0A>>  iterator in PHP. If I can foreach() it an=
d I can call next() on it, I =0A> expect=0A>>  to be able to reset() it as =
well. IMO, you would need to issue a FATAL PHP=0A>>  error if that simply i=
s not allowed. Or you have to have a second syntax =0A> for=0A>>  what to d=
o in that case. At that point, you are implementing Iterator.=0A> =0A> Curr=
ently I'm planning to implement the following behavior for rewind():=0A> =
=0A> * If before first yield: Resume to first yield (this priming behavior=
=0A> is common to all the Iterator methods)=0A> * At first yield: No-op=0A>=
 * After first yield: Recoverable fatal error=0A> =0A> So this would allow =
you to call ->rewind() after creating the=0A> generator, but will throw an =
error if you try to do so later.=0A> =0A> Another thing that I'd like to do=
 is drop the ->close() method. It=0A> doesn't really make sense to explicit=
ly close generators.=0A> =0A> Any objects to those two things?=0A> =0A> Nik=
ita=0A> =0A> -- =0A> PHP Internals - PHP Runtime Development Mailing List=
=0A> To unsubscribe, visit: http://www.php.net/unsub.php=0A>