OpenEuphoria

Re: The fate of Euphoria

• Posted by Ferlin Scarborough <ferlin1 at bellsouth.net> Nov 08, 2004
• 560 views

Mike Nelson 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 tend to somewhat disagree with this, CASE is a glorified If...ElseIf
statement.
You are not really going anywhere, you are saying in the CASE where this is
equal to this, then do this code.  Not goto this other place.  Your program
does not head off in some other direction it still falls through the CASE
statement to the following statement(s).

> 
> On the assembly language level, yes it is. That is of no concern to the
> programmer, however. This code
> 
> if x then
>     do_1()
> elsif y then
>     do_2()
> else
>     do_3()
> end if
> 
> or the equivalent case statements simply do not have the same power or
> potential for abuse as goto:
> 
> 
> if x then
>     goto skip
> end if
> --- 50 other statements
> 
> : skip
> -- 100 other statements
>
<snip> 
> -- Mike Nelson

My biggest beef with the goto statement is that it is usally highly abused,
sometimes to the point where the program is literally unreadable, by the
time you figure out where all those jumps are going to, you could have totally
rewritten an application just like it.

We really don't want to start the goto wars of 4 or 5 years ago on here,
it tended to get pretty nasty, and ending up with each side pretty much
saying, this is my opionion and I'm sticking to it, as stuborn as I am.

Euphoria has lastest this long without the need for a goto, and it will
survive even longer with or without it.  Right now without it, the programs
are much cleaner.

That's my .02 on it.

Later.

Ferlin Scarborough

Learn To Program Games in Free Courses At
http://www.gameuniv.net

My Euphoria Home Page
http://mywebpage.netscape.com/shadetreesoft