Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!rochester!rit!cci632!tvf
From: tvf@cci632.UUCP (Tom Frauenhofer)
Newsgroups: comp.os.minix
Subject: Re: gotos
Message-ID: <31090@cci632.UUCP>
Date: 9 Oct 89 12:31:18 GMT
References: <24984@louie.udel.EDU> <1989Oct6.203815.12548@utzoo.uucp>
Reply-To: tvf@ccird7.UUCP (Tom Frauenhofer)
Organization: CCI, Communications Systems Division, Rochester, NY
Lines: 13

My 2 cents on the goto argument:  The only times I have ever used a goto in
C was when I was in a rush and had to put a quicky fix into some code.
Whenever I go over the code later I invariably find a clearer way to write
the code without a goto.

I'm not anti-goto; I'm pro-readability.  I think goto's take away from the
readability of the code.  Continue statements are worse, especially when
you're an ex-FORTRAN hacker (boy, that'll stir up some controversy, won't
it? :-)

Thomas V. Frauenhofer	...!rutgers!rochester!cci632!ccird7!tvf
*or* ...!rochester!kodak!swamps!frau!tvf *or* ...!attctc!swamps!frau!tvf
"The Earth? I'm going to blow it up.  It obstructs my view of Venus" - Martin