Xref: utzoo comp.bugs.4bsd:1706 comp.lang.c:35724
Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!execu!sequoia!rpp386!jfh
From: jfh@rpp386.cactus.org (John F Haugh II)
Newsgroups: comp.bugs.4bsd,comp.lang.c
Subject: Re: Complexity of reallocating storage (was users command crap)
Message-ID: <19022@rpp386.cactus.org>
Date: 2 Feb 91 14:12:25 GMT
References: <6662@exodus.Eng.Sun.COM> <15325:Jan2903:19:4991@kramden.acf.nyu.edu> <21548@yunexus.YorkU.CA> <5883:Feb102:05:4991@kramden.acf.nyu.edu> <1991Feb2.045119.22199@zoo.toronto.edu>
Reply-To: jfh@rpp386.cactus.org (John F Haugh II)
Followup-To: alt.flame
Organization: Lone Star Cafe and BBS Service
Lines: 15
X-Clever-Slogan: Recycle or Die.

In article <1991Feb2.045119.22199@zoo.toronto.edu> geoff@zoo.toronto.edu (Geoffrey Collyer) writes:
>Dan Bernstein, in response to Ozan Yigit:
>> To rephrase: You don't seem to know what good programming techniques are.
>
>From pty/master.c:

I'm sure it was very hard to write.  Therefore, it should be hard to read,
and hard to maintain, thus promoting job security.

What exactly does it do?
-- 
John F. Haugh II                             UUCP: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 832-8832                           Domain: jfh@rpp386.cactus.org
"I've never written a device driver, but I have written a device driver manual"
                -- Robert Hartman, IDE Corp.