Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77393
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.192.178 as permitted sender)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAPwsocHm4wme7TDX-1hp=PdNGi0KzAwRz4RezW3KddV9_4m=JQ@mail.gmail.com>
Date: Sat, 20 Sep 2014 12:47:43 -0700
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <1A5B2D07-FEC6-410E-85C9-3FBE2F105104@golemon.com>
References: <CAPwsocHm4wme7TDX-1hp=PdNGi0KzAwRz4RezW3KddV9_4m=JQ@mail.gmail.com>
To: Leigh <leight@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Loop... or...
From: php@golemon.com (Sara Golemon)


> On Sep 19, 2014, at 14:56, Leigh <leight@gmail.com> wrote:
> https://wiki.php.net/rfc/loop_or
>=20
I like the general idea, but rather than explicitly focusing on the 'or' key=
word, how about just giving all loop constructs (do/while/for/foreach) a ret=
urn value?  I'd suggest an integer return value indicating the number of tim=
es the loop executed.

This accomodates your use case since foreach(...) {} or { defaultblock } sti=
ll works, while also allowing for others:

e.g.:
$ranTwice =3D foreach(...) {} =3D=3D 2;

It does introduce a temp var, but OpCache+ can trivially optimize that out w=
hen it isn't used.

-Sara=