Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!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: <598@crdos1.crd.ge.COM>
Date: 28 Sep 89 15:15:59 GMT
References: <20324@<1989Sep14> <225800222@uxe.cso.uiuc.edu> <4208@cbnewsh.ATT.COM> <1017@kim.misemi>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: GE Corp R&D Center
Lines: 25

In article <1017@kim.misemi>, kim@kim.misemi (Kim Letkeman) writes:

|  If you keep your programs well structured, with *small* functions that
|  fan out smoothly from control level functions to low level (working)
|  functions, then this situation just doesn't arise. 

  Size and structure are not exclusive. A switch within two for loops
seems like a reasonable structure to me, but it can contain a lot of
cases. If the code for each case is small, say 1-2 statements each,
using a table lookup and procedure per case can add a lot of overhead,
and encourages pollution of global namespace to make variables
available.

  All big procedures are not badly structured, and efforts to keep the
lines per procedure down to some arbitrary limit cost time to write, to
run, and to maintain.

|  I apologize if this message has a pious tone.

  It certainly could be read that way...
-- 
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