Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!ginosko!uunet!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.lang.c
Subject: Re: The final word on GOTO (Don't I wis
Message-ID: <6490@ficc.uu.net>
Date: 10 Oct 89 14:39:35 GMT
References: <20324@<1989Sep14> <225800222@uxe.cso.uiuc.edu> <4208@cbnewsh.ATT.COM> <6396@ficc.uu.net> <526@sunquest.UUCP>
Reply-To: peter@ficc.uu.net (Peter da Silva)
Distribution: na
Organization: Xenix Support, FICC
Lines: 24

The referenced article discusses replacing the Goto with a subroutine call.
The question is raised... why would that reduce clarity?

In a block-structured language it wouldn't. In C, however, there is the
problem of local variables.

Really:

	case whatever:
		special-code...;
		goto common;

Is a lot clearer than:

	case whatever:
		special-code...;
		common(a, whole, bunch, of, random, arguments);
		break;

-- 
Peter da Silva, *NIX support guy @ Ferranti International Controls Corporation.
Biz: peter@ficc.uu.net, +1 713 274 5180. Fun: peter@sugar.hackercorp.com. `-_-'
                                                                           'U`
Quote: Structured Programming is a discipline -- not a straitjacket.