OpenEuphoria

Re: Euphoria features

• Posted by Kat <KSMiTH at PELL.NET> Nov 15, 1999
• 730 views

----- Original Message -----
From: Bernie Ryan <bwryan at PCOM.NET>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Monday, November 15, 1999 4:51 PM
Subject: Re: Euphoria features


> >>I seem to recall that even the K&R text acknowleged that the GOTO is the
> >>best method of expressing that intent.
>
>
>   K&R page 62 section 3.9
>
>   I qoute :
>
>  "C provides the infinitely-abusive goto statement, and labels to branch
to.
>   Formally, the goto is never necessary, and in pratice it is almost
always
>   easy to write code without it."

I think gasoline and automobiles should be eliminated, they both cause
far-reaching negative impact on the environment, and they are implicated in
the deaths of thousands of people each year in the usa. We can all use
horses, bicycles, and helicopters.

>   Then they give two examples one using the goto to get out deeply nested
>   structure and then the second with flags and tests to exit showing
>   that code involving a goto can always be written without one.

But why be forced to make a pile of
if-elsif-elsif-elsif-elsif-elsif-elsif-elsif-elsif-endif when an some
if-gotoend-endif will work?

>   All Euphoria needs two keywords, one that breaks out of a single nested
>   structure and one that breaks out of deeply nested structure. This would
>   would eliminate the abuse of a goto.

And not solve the pile of elsif above. When i give directions to someone on
how to get somewhere, i use "go to", sigh,, i'll need to start forming my
directions into elsif statements just to improve my syle, i guess. <sigh>

Kat