Xref: utzoo misc.misc:6161 comp.misc:6104
Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!wasatch!cetron
From: cetron@wasatch.utah.edu (Edward J Cetron)
Newsgroups: misc.misc,comp.misc
Subject: Re: The "evil" GOTO (Was: 25 Years of BASIC)
Message-ID: <1825@wasatch.utah.edu>
Date: 15 May 89 00:21:39 GMT
References: <1791@ubu.warwick.UUCP> <1436@onion.reading.ac.uk> <1814@ubu.warwick.UUCP> <24044@agate.BERKELEY.EDU> <2861@cps3xx.UUCP> <1745@wasatch.utah.edu> <4396@ttidca.TTI.COM>
Organization: Morrison-Knudsen, Industrial Buildings Division, SLC, UT
Lines: 16

In article <4396@ttidca.TTI.COM> hollombe@ttidcb.tti.com (The Polymath) writes:
-In article cetron@wasatch.utah.edu (Edward J Cetron) writes:
-}	This entire GOTO debate seems to be indicative of the quality of 
-}programmers currently available today.  To them, STRUCTURE is EVERYTHING.
-When I'm concerned about machine efficiency, I write in assembler. (I've
-written a _lot_ of assembler on some projects).  In my current
-environment, I'm concerned about portability.
-
-There are always tradeoffs.

	My point exactly - there are ALWAYS tradeoffs, but unless you have
been trained/educated to realize that there are tradeoffs (and then to
understand how to evaluate them), you have missed the boat.

-ed cetron
cetron@wasatch.utah.edu