Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77835
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain pascal-martin.fr designates 176.31.99.170 as permitted sender)
Message-ID: <5436FC32.2070704@pascal-martin.fr>
Date: Thu, 09 Oct 2014 23:20:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAPwsocFzuaKbsT_j6-3f5=7qj6mpvudzcBbjKjW=7PRqOBhm6w@mail.gmail.com>
In-Reply-To: <CAPwsocFzuaKbsT_j6-3f5=7qj6mpvudzcBbjKjW=7PRqOBhm6w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] [RFC] Loop + or control structure
From: mailing@pascal-martin.fr ("Pascal Martin, AFUP")

On 03/10/2014 22:33, Leigh wrote:
> Opening the vote on loop + or control structures.
>
> https://wiki.php.net/rfc/loop_or
>
> Voting will close in 1 week and requires a 2/3 in favour to pass.
>
> Remember at this stage the implementation is flexible.
>

Hi,

After talking with other members of AFUP, it seems most of us like the 
idea of having some way of executing code if a loop is never executed.

The "or" keyword feels a bit odd to those who are used to the "else" of 
Twig (or other languages) -- but it's not really that much of a problem 
either: after a while, we'll get used to using "or" (or some other keyword).

So, we would be on the +1 side of things on this.


Still, Sara's idea of giving all loop constructs a return value 
indicating the number of times the loop executed feels great -- and this 
would probably be more flexible than loop...or

I'm guessing this is why you voted "no" on your own RFC?

-- 
Pascal MARTIN, AFUP - French UG
http://php-internals.afup.org/