Re: Re: GOTO and/or BREAK LABEL (conclusion)

From: Date: Thu, 09 Mar 2006 20:12:30 +0000
Subject: Re: Re: GOTO and/or BREAK LABEL (conclusion)
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to internals+get-22307@lists.php.net to get a copy of this message
The reason for using jump is "because it is not a full analog of C's goto statement". It's my guess that experienced developers will want to lookup what the behaviour in PHP is.
Cool. You just gave an excellent argument for not calling it 'goto' :) Seriously, the manual entry will probably use the word 'goto' in the description, and this will show up on search engines. But if we have a manual entry named 'goto', whether it be a dummy entry or not, Zeev's nightmare scenario re new users and spaghetti code has a good chance of coming true. It's the one command just about everyone's heard of. - Steph

« previous php.internals (#22307) next »