Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_compile.c zend_compile.h zend_globals.h zend_language_parser.y /tests break_label01.phpt
break_label02.phpt break_label03.phpt break_label04.phpt break_label05.phpt break_label06.phpt

From: Date: Sat, 04 Mar 2006 03:25:01 +0000
Subject: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_compile.c zend_compile.h zend_globals.h zend_language_parser.y /tests break_label01.phpt
break_label02.phpt break_label03.phpt break_label04.phpt break_label05.phpt break_label06.phpt
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.zend-engine.cvs 
Request: Send a blank email to [email protected] to get a copy of this message 
sorry, it seems i've missed some splitted threads on this topic that u
guys decided with goto only. but still, it would be nice for a real
labele break beside goto.

On 3/4/06, Xuefer <[email protected]> wrote:
> that means everyone can
> do {
>  break label;
> } while (0);
> to simulat exactly what goto gives u...
> the 1st time i mention labeled break is really for "exit/escape from
> deep constructs" only.
> although it's logical in the implemention, it doesn't mean it's also
> logical from the php language design.
> i'd suggest that one can only do forwared break (to the label after
> the break statement), and even make require the label to be
> immediately after one construct (for/while/switch/foreach). whenever u
> read a "break", "break number" "break label", u know it's a
> break not
> goto, always.
> if u guys like goto function, just implement, don't put eveything on
> labeled break.
>

Thread (28 messages)

« previous php.zend-engine.cvs (#4665) next »