Re: GOTO operator
| From: | Derick Rethans | Date: | Tue, 03 Aug 2004 13:46:54 +0000 |
| Subject: | Re: GOTO operator | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-11873@lists.php.net to get a copy of this message | ||
On Tue, 3 Aug 2004 Derrell.Lipman@UnwiredUniverse.com wrote:
> Andi Gutmans <andi@zend.com> writes:
>
> > I don't think we should be using computed targets. It'd be more of a
> > nightmare than sexy. I prefer doing as much at compile-time as possible and
> > I don't think that allowing indirect goto's would lead to anything than
> > chaos. Most arguments in favor of goto were for circumstances where this
> > would not be required. (And yes, even if we pre-compute what we can and add
> > the hash and opcode for the instances we can't pre-compute I think it's a
> > very bad idea). I feel about 1000 times stronger about that than goto :)
>
> If you really, really, really wanted to do such a thing, you could still do:
>
> eval("goto foo$bar;");
>
> to get the same effect, right?
Hmm, depends on how it's implemented. It will most likely not work I
guess.
Derick