Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!zehntel!hplabs!hpda!fortune!amdcad!decwrl!decvax!bellcore!allegra!mit-eddie!godot!ima!ISM780!rick
From: rick@ISM780.UUCP
Newsgroups: net.lang.c
Subject: Re: break <label> and another use for go
Message-ID: <38@ISM780.UUCP>
Date: Thu, 17-Jan-85 04:46:09 EST
Article-I.D.: ISM780.38
Posted: Thu Jan 17 04:46:09 1985
Date-Received: Tue, 22-Jan-85 03:49:34 EST
Lines: 20
Nf-ID: #R:decvax:-2300:ISM780:12500033:000:858
Nf-From: ISM780!rick    Jan 16 11:39:00 1985

>> 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 :-)

Not to belabor the point, but macros can be used to create "subroutines"
that don't have any linkage overhead.

						-- Reg