Re: Re: GOTO and/or BREAK LABEL (conclusion)
| From: | Zeev Suraski | Date: | Thu, 09 Mar 2006 18:10:20 +0000 |
| Subject: | Re: Re: GOTO and/or BREAK LABEL (conclusion) | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-22300@lists.php.net to get a copy of this message | ||
At 19:37 09/03/2006, Pierre wrote:
On 3/9/06, Steph Fox <steph@zend.com> wrote:Uhm, of course you can. Avoiding problems is by far the best way of solving them. But it has nothing to do with our topic. ZeevBdB>>Even though I like "jump", people will most likely be searching for BdB>>"goto" (PHP manual) or "goto PHP" (Google) when they're trying to BdB>>find out if PHP has such a functionality. So, maybe it's better to BdB>>just call it "goto". For such people we might have a page in the manual saying: goto: see jumpErm, wouldn't those people who need to refer to the manual be exactly the same people we wanted to protect from goto in the first place? :) jump +1, if it counts You are back to the main problem, you cannot educate people by keeping them away from the "dangerous" functions.