OpenEuphoria

Re: The fate of Euphoria

• Posted by Patrick Barnes <mrtrick at gmail.com> Nov 08, 2004
• 547 views

On Mon, 8 Nov 2004 10:15:04 -0600, Kat <gertie at visionsix.com> wrote:
> It's another goto in disguise. So is the elsif, for that matter. Picture the
> little
> goto at the end of each elsif that executes in that stack of if-elsif-end,
> where
> the goto points to the end of the stack.

I know that all program flow statements resolve to "jmp" or similar
when converted down to assembly language, but luckily we don't have to
think in assembly constructs all the time... I'm very happy Rob hasn't
said "No if-statements"!

If I may ask, Kat, what can be done with goto that can't be done with
the higher-level constructs? There are some high-level constructs
missing from Euphoria at the moment, so assuming that you have:
if/elsif/else switch/case/exit  while/for exit/next exit(N)/next(N)
available, can you give me an example of something that can't be done
using them, that needs a goto?

Please note, this is not an attack of any kind, I would like to see if
it has uses. In my job I make changes to existing C/C++ code, and
rarely do I see a goto. Perhaps the world would not end if Rob added
goto to the language, no programmer with enough skill to write
libraries that others would find useful would be silly enough to use
them in a way that should be done with a simple higher-level
construct.

-- 
MrTrick