>Is it also true that gotos take a lot of time to process, especially in
a-time?  I think another argument is that often the types of projects that
^^^^ a-time?? r=run c=compile what's a==?
well unless the compiler does something funky the 'goto' statement could
be just a simple ML jmp (direct) to another memory address ( umm performed
in 1 [or less?] cpu cycle ( fast )
>>
the essence, so to speak.  I think I'll jump on the bandwagon here and
speak in favor of the statement block idea.  I'm no expert on programming
languages (I'm in my fifth week of a college C Programming course) but
there must be some more elegant way of doing this, right?  It seems rather
inefficient to me to have my program jumping around everytime there is a
little trick to perform.  Anyway, just a suggestion.  I'm afraid I don't
have enough programming know-how to work out any details.
 >>
real problem with gotos is the undisciplned hackers who write spaghetti
code that is TUFF to follow ( in software engineering they call this