Path: utzoo!mnetor!uunet!vsi!sullivan
From: sullivan@vsi.UUCP (Michael T Sullivan)
Newsgroups: comp.lang.c
Subject: Re: gotos
Message-ID: <509@vsi.UUCP>
Date: 8 Apr 88 20:29:20 GMT
References: <2571@cognos.UUCP> <77200029@uiucdcsp> <4307@ihlpf.ATT.COM> <2556@ttrdc.UUCP>
Organization: V-Systems, Inc. -- Santa Ana, CA
Lines: 42

In article <2556@ttrdc.UUCP>, levy@ttrdc.UUCP (Daniel R. Levy) writes:
> I know this battle is an old chestnut, but for the record do you guys believe
> that superfluous flags and great big if-then statements are truly superior
> to the goto?  (And the break, which is a goto by another name.)  E.g.:
> 
> 	while (loopcond) {
> 		for (i=0; i<limit; i++)
> 			if (frob(i) == TRUE)
> 				goto loopagain;	/* nice and CLEAN!!! */
> 		...
> 		/* lots and lots of code over many pages */
> 		...
> loopagain:	;
> 	}

	while (loopcond)
	{
		flag = FALSE;
		for (i=0; i<limit; i++)
		{
			if (frob(i))
			{
				flag = TRUE;
				break;
			}
		}
		if (flag)
			continue;
		...
		/* lots and lots of code over many pages */
		...
	}

You don't have to spin your wheels in a for loop and you don't have to use
the goto.  I should think if you can avoid a goto, do it.  Some people
believe gotos are inherently not "nice and CLEAN!!!".  But as you say, this
is an old chestnut.

-- 
Michael Sullivan		{uunet|attmail}!vsi!sullivan
				sullivan@vsi.com
HE V MTL