Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!charyb!dan
From: dan@charyb.COM (Dan Mick)
Newsgroups: comp.unix.questions
Subject: Re: How to flush output (was how ... to disk)
Message-ID: <339@charyb.COM>
Date: 9 Dec 89 21:26:12 GMT
References: <606@caldwr.UUCP> <1025@friar-taac.UUCP> <4176@sbcs.sunysb.edu> <333@charyb.COM> <21184@mimsy.umd.edu>
Reply-To: dan@charyb.UUCP (Dan Mick)
Distribution: usa
Organization: KFW Corporation, Newbury Park, CA
Lines: 18

In article <21184@mimsy.umd.edu> chris@mimsy.umd.edu (Chris Torek) writes:

(about using setbuf(stdout, NULL)

>... and slow.  I mean *really* slow.  I mean, really truly HORRIBLY
>slow.  I mean, if you think the city buses are slow. . . .

Yes, you're absolutely right.  I'd thought he was looking for output whilst
debugging; I don't have any idea how I got that notion locked in my head.
Sorry.  Of course it's horribly inefficient.

While debugging, I don't care, and it involves virtually no source mods, 
so it's far easier to stick in as a temporary change.  But you wouldn't wanna
do it for a finished program.

Sorry for the confusion.  Some humility probably doesn't hurt me, anyway.
-- 
.sig files are idiotic and wasteful.