Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20873
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <D2.10.14828.9585D834@pb1.pair.com>
To: internals@lists.php.net
References: <2B.E1.14828.4130D834@pb1.pair.com> <7f3ed2c30511292327p1ffae378n9c2bfb01bdb333d3@mail.gmail.com>
Date: Wed, 30 Nov 2005 08:39:47 +0100
Lines: 103
Subject: Re: [PHP-DEV] Labeled Break (nothing at all whatsoever to do with GOTO)
From: r.korving@xit.nl ("Ron Korving")

I loved Joao Cruz Morais idea of using the 'as' keyword in this:

while (true) as outer_cycle {
  $i = 0;
  while (true)
    if($i++ == 10) break outer_cycle;
}

I think it's really clear and with this syntax you (at least in my opinion) 
kinda loose the feeling of needing all caps for a label name. Somehow it 
feels less like a constant. This is absolutely personal though, and could be 
just between my ears, not yours... I just love this syntax ;)

Ron



"Hannes Magnusson" <hannes.magnusson@gmail.com> schreef in bericht 
news:7f3ed2c30511292327p1ffae378n9c2bfb01bdb333d3@mail.gmail.com...
Elegant solution, however, I'd prefer while(true) FOO { }.

while FOO(true) {} looks like a function call...

On 11/30/05, Sara Golemon <pollita@php.net> 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;
> }
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>