Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.questions
Subject: stdio output flush (was re-directing 'rup' to a file)
Message-ID: <10605@dog.ee.lbl.gov>
Date: 5 Mar 91 13:20:57 GMT
References: <1991Mar5.014821.1555@unixland.uucp> <1991Mar05.080251.15424@convex.com>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 16
X-Local-Date: Tue, 5 Mar 91 05:20:57 PST

In article <1991Mar05.080251.15424@convex.com> tchrist@convex.COM
(Tom Christiansen) writes:
>...I think that this is just a hack
>around a problem caused by lack of design forethought in stdio:
>you shouldn't need a whole pty just to get line buffering!

In my opinion, the design flaw is that line buffering exists.  Indeed,
any kind of buffering other than `full'---unbuffered output should just
be a last-resort-buffer-size-equals-one trick, much the way I
implemented it myself---is just a complication that leads to this sort
of bad behaviour.

But there is nothing I can do about that. . . .
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab EE div (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov