Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:11676
Return-Path: <pollita@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 59979 invoked by uid 1010); 30 Jul 2004 17:20:18 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 59828 invoked by uid 1007); 30 Jul 2004 17:20:17 -0000
Message-ID: <20040730172017.59787.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <20040729021337.73894.qmail@pb1.pair.com> <200407291531.32614.alex.pagnoni@solarix.it> <4109ACC6.4040100@leetspeak.org> <200407301012.11170.alex.pagnoni@solarix.it>
Date: Fri, 30 Jul 2004 10:19:35 -0700
Lines: 20
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Posted-By: 64.142.6.231
Subject: Re: [PHP-DEV] GOTO operator
From: pollita@php.net ("Sara Golemon")

> But reading the various posts here, I changed a little my opinion. I'm in
> favor of a goto operator if the "scope" of its labels is limited to, say,
a
> function/method only.
>
And that's precisely how this implementation of GOTO behaves.  You can only
jump to a label within the same op array. That means:

*) No jumping between functioncs
*) No jumping into/out-of the global scope
*) No jumping from any code in one file to code in another file (even if
it's global scope on both ends)

This is (roughly speaking) the same as C's rules under which you can only
jump within a function.  (Execution within a global scope doesn't really
apply).

-Sara