Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62281
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.170 as permitted sender)
Message-ID: <503225D8.4040900@gmail.com>
Date: Mon, 20 Aug 2012 13:56:08 +0200
User-Agent: Thunderbird
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@lerdorf.com>
CC: Stas Malyshev <smalyshev@sugarcrm.com>, 
 Derick Rethans <derick@php.net>,
 Nikita Popov <nikita.ppv@gmail.com>, 
 PHP internals <internals@lists.php.net>
References: <CAF+90c_pRo6Xs2Cv9X-BN3mSnHi65gHHWzD8+yOnAPqgnWJm_w@mail.gmail.com> <alpine.DEB.2.02.1208181312390.24463@whisky.home.derickrethans.nl> <503171CB.3090609@sugarcrm.com> <50317E51.4090305@lerdorf.com>
In-Reply-To: <50317E51.4090305@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Generators
From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=)

On 20/08/12 02:01, Rasmus Lerdorf wrote:
> I would still like to understand what this generator keyword would
> actually do. I don't see how it would work. Would a function marked
> generator somehow not be allowed to return normally or to finish and not
> return anything? How could this be enforced? I am completely against any
> keyword that is essentially documentation-only.
>
> -Rasmus
Given that such function could "return several times", seems a different
enough function type to have its keyword.
You could not decorate it and rely instead on the presence of the yield
keyword, but parsers will thank knowing about it from the start rather
than realising at mid-parsing that the function is a completely
different beast.

Regards