OpenEuphoria

Re: When it comes to GOTOs...

• Posted by Hawke <mdeland at NWINFO.NET> Sep 27, 1998
• 437 views

Matt Z Nunyabidness wrote:
>hey, if RDS adds a GOTO statement to Euphoria,
>what does that have to do with you?
everything.
Euphoria is created by RDS. SO? you ask?
RDS is *RAPID* Deployment Software.
See the RAPID there?
That is a two-fold moniker in my opine.
Not only does Euphoria allow you to create a
program in short order, but to paraphrase
Father Euphoria, succinctly, Euphoria is
    ****FAST****
Why is it fast? Because it doesn't have any
bloody GOTO's and other constructs that serve
to only clutter a language.
So, it has everything to do with me.  If requests
for additions to Euphoria are to be made, don't
you think you outta list *why* you want it?

Can a goto statement meet all of the following:

  Generally agreed upon by members of this list,
  as well as Father Euphoria, minimum requirements
  for consideration of a construct suggestion that
  the suggester desires to be included within the
  core of the Euphoria language:
    1> Does it make code more readable? ( +1)
    2> Does it make code less readable? (-10)
    3> Does it improve maintainability? ( +1)
    4> Does it hinder maintainability?  (-10)
    5> Does it improve performance?     ( +2)
    6> Does it hinder performance?      (-20)
    7> Does it improve portability?     ( +1)
    8> Does it hinder portability?      (heh, what portability?) ;)
    9> Will it actually be used???      ( +5)
   10> Does Rob want it in there?       (+50)
   11> Does Rob not want it in there?   (-99)
After adding your score, if you actually come out positive,
then ask the last questions:
    1>Does it *have* to be in the core, or can it be an include?
If that answer is yes, ignore 1-9, don't pester Rob cuz he's
busy with EU3, make a short post on the list as to where
your include can be found, or if it's a small (<10K) zipfile
then most won't mind simply directly posting it.

Let's score GOTO shall we? ;)
 1>   0 --doesn't help readability
 2> -10 --def'nly hurts readability
 3>   0 --doesn't help maintainability
 4> -10 --def'nly hurts maintainability
 5> 0.5 --in theory, at certain perfect moments, it can help speed
 6>  -5 --usually hurts performance, cache's get thrashed
 7>   0 --doesn't really help portability, we have routine_id
 8> N/A --doesn't hinder it either
 9> 0.1 --on a good day, less than 1% of the EU population will use it
10>   0 --he don't want it in there
11> -99 --oops!
------------
  -123.4 for the case for GOTO

To sum up:
GOTO can be made as an include! [ see dave? only 1 ! :) ]
(see routine_id and the listserv archives about the case
 statement and the algorithm used for that, it was slick)
So, please end this thread.

--Hawke'