Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20883
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <AA.64.14828.88C6D834@pb1.pair.com>
To: internals@lists.php.net
Date: Wed, 30 Nov 2005 10:11:11 +0100
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
References: <2B.E1.14828.4130D834@pb1.pair.com>
In-Reply-To: <2B.E1.14828.4130D834@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Labeled Break (nothing at all whatsoever to do with GOTO)
From: bart@mediawave.nl (Bart de Boer)

Sara++  :)

Although I prefer BAR:while (This would go better with goto if someone 
would want to implement that some day.) I'd settle for while BAR since I 
don't care about goto anyway.

So:

foreach BAZ ($arr as $val) +1


BAZ: foreach ($arr as $val) +2


foreach as BAZ ($arr as $val) -2 ('as' can be a bit confusing here)




Sara Golemon wrote:
> But first, this word from our sponsor:
> Group A wants anything resembling goto to burn in the fires of hell
> Group B wants full non-crippled goto or nothing at all
> Group C wants partial goto (non-backward jumping) or nothing at all
> Groups B and C both (generally) want it called either GOTO or JUMP, not
> BREAK
> 
> Since no group this size will ever come to an agreement on something this
> divisive, I'd like to turn the topic to a completely different language
> feature which (might) please enough people to get a rousing consensus.
> 
> Actual labeled breaks.  Not the break+jump that was proposed earlier in the
> guise of a break statement, but an actual straightforward, no funny-business
> labeled break which does no more and no less than the current break N;
> construct, but allows the use of identifier labels rather than numbers which
> may change as the result of the addition or removal of break containers.
> 
> http://libssh2.org/patches/true_labeled_break.diff
> 
> Usage:
> 
> while FOO ($condition) {
>     /* statements */
>     break FOO;
>     /* more statements */
> }
> 
> Or a stacked example:
> 
> for FOO(;;) {
>     while BAR (true) {
>         foreach BAZ ($arr as $val) {
>             switch Foof ($value) {
>                 default:
>                     do Plop {
>                         break FOO;
>                     } while (false);
>             }
>         }
>     }
> }
> 
> Notes on this implementation:
> 
> * Labels can't be repeated in an ancestral line.  For example, the parser
> will throw an ERROR on the following:
> while FOO(true) {
>     while FOO(true) {
>         break FOO;
>     }
> }
> 
> * Labels can be repeated by siblings.  I'm not married to this, and it
> certainly has WTF potential.  This behavior is easily modified to throw an
> error.  I left it permissable because there was no technical reason to
> disallow it.  For example, the following is okay:
> while FOO(true) {
>     break;
> }
> while FOO(true) {
>     break FOO;
> }
> 
> * Labeled breaks also apply to continue;  For example:
> foreach FOO($arr as $key => $val) {
>     if ($key % 2) continue FOO;
>     if (empty(%key)) break FOO;
> }