Xref: utzoo comp.bugs.4bsd:1703 comp.lang.c:35697
Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!spool.mu.edu!uwm.edu!lll-winken!sun-barr!rutgers!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.bugs.4bsd,comp.lang.c
Subject: Re: Complexity of reallocating storage (was users command crap)
Message-ID: <5883:Feb102:05:4991@kramden.acf.nyu.edu>
Date: 1 Feb 91 02:05:49 GMT
References: <6662@exodus.Eng.Sun.COM> <15325:Jan2903:19:4991@kramden.acf.nyu.edu> <21548@yunexus.YorkU.CA>
Organization: IR
Lines: 17

In article <21548@yunexus.YorkU.CA> oz@yunexus.yorku.ca (Ozan Yigit) writes:
> To rephrase: ... you are using poor programming techniques. No program
> should make multiple passes over a disk file when it could accomplish its
> task with a single pass with hardly any effort on the programmer's part.

If you spent a minute putting your priorities into order you'd realize
that this is an entirely ridiculous generalization. If two programs are
just as fast, just as small, and take just as little programmer (and
user) effort, then it simply doesn't matter whether one of them uses
more passes than the other.

To rephrase: You don't seem to know what good programming techniques
are. Tradeoffs between speed, space, and human effort are important.
Tradeoffs between ``multiple passes'' and ``single pass'' are entirely
irrelevant when they aren't reflected in speed, space, or human effort.

---Dan