"Sara Golemon" <[EMAIL PROTECTED]> writes:
>> > 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.
>>
> Nope... eval()'d code is in a separate op_array from the code it's eval()'d
> from. While it has the same variable scope it does not have the same label
> pool. Building in that kind of support is theoretically doable (and you'd
> get support for cross-file gotos in the process), but it complicates the
> execution flow somethin' fierce.
My contention was that eval() should work consistently. Andi indicated that
there are other language features which would similarly not "work" when
eval()'ed. If that's the case, then not having this work as well, is fine
with me. (I voted -1 on variable labels even though I voted +1 on goto.)
Out of curiosity, I wonder which other features would similarly not work when
eval()'ed...???
Cheers,
Derrell
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
