Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.lang.c
Subject: Re: The final word on GOTO (Don't I wis
Message-ID: <514@crdos1.crd.ge.COM>
Date: 26 Sep 89 12:19:16 GMT
References: <20324@<1989Sep14> <225800222@uxe.cso.uiuc.edu> <4208@cbnewsh.ATT.COM>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: GE Corp R&D Center
Lines: 18

In article <4208@cbnewsh.ATT.COM>, ijk@cbnewsh.ATT.COM (ihor.j.kinal) writes:

|  Well, what if it took the NEXT poor programmer who maintains  that
|  program an extra week to understand what it does ???  Or even
|  an extra minute ??? [each and every time it was examined - it might
|  add up to a lot].

  It depends on what you use instead of the goto. If you compare a goto
against setting a flag variable and testing it to break out of three
levels of loop, the goto is certainly easier to understand, particularly
if the loops have a lot of code. If you use a goto where a break would
do it makes the code more subject to error (you can now mess up
placement of the goto or the label).
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
"The world is filled with fools. They blindly follow their so-called
'reason' in the face of the church and common sense. Any fool can see
that the world is flat!" - anon