Re: Euphoria features
Lucius, Ralf, Kat
When you goto out of a "for" or a "while", you leave the statement in
an uncertain status if you do not go through some form of termination
of the for or while structure, including garbage collection. Very little
in practical reality is saved. Also, in Euphoria, I would like to know where
to you would go. The only thing that resembles a label or address in
Euphoria is a procedure name. If you goto a procedure, where will you
return to. If you goto a function name to whom will you return the value
and where will you return to. It appears that Euphoria was designed
to be goto proof. Now, we need not only goto's, but labels.
In addition, nobody has addressed my question about the scoping
effects of gotos. When you goto from the middle of a function or a
procedure to some other location that would normally have a
hierarchically built scope, how do you reestablish that scope? How do
you collapse the scope that you are leaving? Euphoria is a block
structured language, and I imagine the interpreter is built around
the initializing and closing of those blocks. If goto out of a block structure
does not close that block, what happens to it? If it does, what have
I gained? If blocks can only be entered at the top, does Euphoria
entirely depend on the initialization code to clear a block? Things like
exit argue otherwise.
Just a few questions to rock you to sleep with.
Everett L.(Rett) Williams
rett at gvtc.com
|
Not Categorized, Please Help
|
|
