Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77836
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5436FC32.2070704@pascal-martin.fr>
References: <CAPwsocFzuaKbsT_j6-3f5=7qj6mpvudzcBbjKjW=7PRqOBhm6w@mail.gmail.com>
	<5436FC32.2070704@pascal-martin.fr>
Date: Thu, 9 Oct 2014 22:49:57 +0100
Message-ID: <CAPwsocHp5ru3sNeZhkzS0-g30nMWR+LKEB8s8gMOmfR1tfcZ0g@mail.gmail.com>
To: "Pascal Martin, AFUP" <mailing@pascal-martin.fr>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [VOTE] [RFC] Loop + or control structure
From: leight@gmail.com (Leigh)

On 9 October 2014 22:20, Pascal Martin, AFUP <mailing@pascal-martin.fr> wrote:
>
> I'm guessing this is why you voted "no" on your own RFC?
>

Getting this feature working was the result of several compromises,
and I didn't like the idea of feeling like "I wish this was different,
oh wait... it's my fault..." every time I used it.

It really did boil down to syntactic sugar. There was a small
performance gain on large loops compared to using a tracking variable,
but it wasn't really enough to overcome my negative feelings towards
it.

The groundwork and proof of concept patch is there. If someone else
knows how to make it sexy, they're free to pick it up and run with it
:)