Xref: utzoo misc.misc:6034 comp.misc:6011
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!ames!hc!lll-winken!uunet!philmtl!philabs!ttidca!hollombe
From: hollombe@ttidca.TTI.COM (The Polymath)
Newsgroups: misc.misc,comp.misc
Subject: Re: The "evil" GOTO (Was: 25 Years of BASIC)
Message-ID: <4383@ttidca.TTI.COM>
Date: 8 May 89 21:02:20 GMT
References: <1814@ubu.warwick.UUCP> <13113@lanl.gov> <2854@cps3xx.UUCP>
Reply-To: hollombe@ttidcb.tti.com (The Polymath)
Organization: The Cat Factory
Lines: 18

In article <2854@cps3xx.UUCP> rang@cpswh.cps.msu.edu (Anton Rang) writes:
}... Actually, I feel that 'break' should usually be replaced by
}an explicit goto (heresy!).  Why?  Because the place the break goes to
}isn't explicit; you have to start matching up loops.  ...

Where the break goes is _very_ specific.  It gets you out of the innermost
containing loop (or switch).  Where a goto goes is _anywhere_ it damn well
wants to.  I'd much rather match up a few braces (which, in _my_ coding
standard, are aligned vertically on the page) than search through thousands
of lines of code for a goto label.  Not to mention finding such a label in
the middle of a program and wondering how many goto statements go to it
and where they are.

-- 
The Polymath (aka: Jerry Hollombe, hollombe@ttidca.tti.com)  Illegitimati Nil
Citicorp(+)TTI                                                 Carborundum
3100 Ocean Park Blvd.   (213) 452-9191, x2483
Santa Monica, CA  90405 {csun|philabs|psivax}!ttidca!hollombe