OpenEuphoria

Re: Good Use of GOTO

• Posted by Jeremy Cowgar <jeremy at c?wg?r.com> Jun 06, 2008
• 855 views

c.k.lester wrote:
> 
> Jeremy Cowgar wrote:
> > c.k.lester wrote:
> > > It has never been demonstrated that a Euphoria developer needs the
> > > ability.
> > CK, did you actually read any of the links I gave in a previous post?
> 
> Yes I did. None of them were convincing arguments for adding GOTO to Euphoria.
> 

Convincing to who? Others have already commented otherwise. Convincing to you?
I'm not sure a 15,000% speed increase and 98% line count reduction would convince
you.

> 
> Again, the need for benchmarking is evident. :)
>

Go ahead then and benchmark a function call. Then benchmark just the function
body inside of a for loop.
 
> 
> I kinda disagree. I think GOTO is easier to abuse. It's unstructured. You can
> use it to go anywhere from anywhere. The if/while/for/etc. is far more
> structured and you are limited to what kind of damage you can do accidentally.

Easier than an include file? For instance, you had to do a code clean up in
BBCMF due to include usage, and I'm not picking on you, it was just pretty easy
to abuse. I think therefore we should go to a monolithic structure where all code
is in one file.

--
Jeremy Cowgar
http://jeremy.cowgar.com