Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!adm!PEPRBV%CFAAMP.BITNET@husc6.harvard.EDU
From: PEPRBV%CFAAMP.BITNET@husc6.harvard.EDU (Bob Babcock)
Newsgroups: comp.lang.c
Subject: Re: info-c digest vol 1 number 43
Message-ID: <12930@brl-adm.ARPA>
Date: 12 Apr 88 16:47:57 GMT
Sender: news@brl-adm.ARPA
Lines: 11

<tainter@ihlpg.ATT.COM> writes
>People, listen closely, GOTOs are not inherently bad.  If used carefully
>as in this example they are quite reasonable and really not hard to follow.
>Of course, they would be much harder to understand if they didn't use
>mnemonics and instead used numbers ala Pascal or ForTran.

Ever try to find where  a goto was going in a sloppy,  multi-page
program (any language)?  The Fortran GOTO 100 is easier to trace,
provided  you  have  run  the  code  through  a  processor  which
renumbers statements rationally.   (I wouldn't want to even think
about working on Fortran code without such a processor.)