Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version nyu B notes v1.5 12/10/84; site acf4.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!teddy!panda!talcott!harvard!seismo!cmcl2!acf4!greenber
From: greenber@acf4.UUCP (ross m. greenberg)
Newsgroups: net.lang.c
Subject: Re: break <label> and another use for goto's.
Message-ID: <800001@acf4.UUCP>
Date: Mon, 14-Jan-85 08:59:00 EST
Article-I.D.: acf4.800001
Posted: Mon Jan 14 08:59:00 1985
Date-Received: Tue, 15-Jan-85 05:41:23 EST
References: <23@decvax.UUCP>
Organization: New York University
Lines: 21

henry@utzoo.UUCP=>

> If it's
> long enough to make tracking indenting levels difficult, it's too
> long to be in one monolithic piece.

I disagree.  If the piece of code is time critical or used ALOT, then
the extra calls to subroutines might become too much overhead.  There was
a piece of code I had the misery to maintain a while back that had only
about TWELVE levels of nesting.  Try as I could I couldn't break it out
into more efficient code, just easier to look at code.  The ratio of
ridiculous nesting level time to fun-to-look-at code was somewhere about
1.6:1, and I couldn't afford the extra time as this was a psuedo-realtime
job.

Of course, I did change tabbing to just a few spaces, so I didn't have
to use two tubes :-)


------------------------------------------------------
Ross M. Greenberg  @ NYU   ----> { allegra,ihnp4 }!cmcl2!acf4!greenber  <----