Xref: utzoo misc.misc:6013 comp.misc:6000
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!indri!uflorida!novavax!twwells!bill
From: bill@twwells.uucp (T. William Wells)
Newsgroups: misc.misc,comp.misc
Subject: Re: The "evil" GOTO (Was: 25 Years of BASIC)
Keywords: Guinness, phlegm, mackerel, intestines
Message-ID: <910@twwells.uucp>
Date: 6 May 89 23:11:45 GMT
References: <1791@ubu.warwick.UUCP> <1436@onion.reading.ac.uk> <24047@agate.BERKELEY.EDU> <103199@sun.Eng.Sun.COM>
Reply-To: bill@twwells.UUCP (T. William Wells)
Organization: None, Ft. Lauderdale
Lines: 18
Summary:
Expires:
Sender:
Followup-To:
Distribution:

In article <103199@sun.Eng.Sun.COM> falk@sun.Eng.Sun.COM (Ed Falk) writes:
: YUK!  This is getting worse and worse.  A "return" is basicly a
: GOTO to the end of the function.  Besides being nit-picky, there's
: a LOT of reasons not to put returns in the middle of code; you're
: sure to get bitten by that habit.  Supposing you later come back
: and modify this function to allocate some resource and then free it
: at the end before returning.  If you don't notice a return in the
: middle of your code, you start eating resources.

Not reasonable. The "search" key in your favorite editor will easily
spot return. A failure to look for them is simply bad programming.

No, this is yet another example of misguided structured programming
ideology; the reasons for this went away when punch cards ceased to
be the normal method of entering programs.

---
Bill                            { uunet | novavax } !twwells!bill