Path: utzoo!attcan!uunet!lll-winken!xanth!mcnc!ecsvax!phco
From: phco@ecsvax.UUCP (John Miller)
Newsgroups: comp.misc
Subject: Re: The "evil" GOTO (Was: 25 Years of BASIC)
Message-ID: <6974@ecsvax.UUCP>
Date: 10 May 89 13:11:56 GMT
References: <1791@ubu.warwick.UUCP> <1436@onion.reading.ac.uk> <1814@ubu.warwick.UUCP> <698@occrsh.ATT.COM> <852@umecs.cs.umu.se> <132@quad.uucp>
Reply-To: phco@ecsvax.uncecs.edu.UUCP (John Miller)
Organization: Univ. of North Carolina at Chapel Hill
Lines: 25

>where we're going...  ;')
>
>    goto LOCATION;
>
Here's another code segment (label only):

     LOCATION:

Now, quick, tell me where we're coming from!  In many cases the mere
existence of a label can be more confusing than the presence of a "goto"
because it implies an unknown number of jumps from multiple unknown
locations.  

If you have to have a label in your code, put a comment with it to
explain why it's there, e.g.,

     LOCATION:    /* here begins code for handling abnormal termination
                     (i.e., goto) of function blah() or function huh() */


-- 
                        John Miller  (ecsvax!phco)
                        Dept. of Pharmacology, Univ. of N.C.-Chapel Hill
			CB#7365   1026A FLOB
                        Chapel Hill, NC 27599       (919) 966-6966