Xref: utzoo comp.sys.amiga.tech:1496 comp.lang.c:11823
Path: utzoo!utgpu!attcan!uunet!husc6!rutgers!bellcore!tness7!tness1!sugar!peter
From: peter@sugar.uu.net (Peter da Silva)
Newsgroups: comp.sys.amiga.tech,comp.lang.c
Subject: Re: Lattice C 4.0 bugs
Summary: The bug is... line buffered streams are a bad idea.
Message-ID: <2458@sugar.uu.net>
Date: 12 Aug 88 16:27:46 GMT
References: <6627@bloom-beacon.MIT.EDU> <3750@ece-csc.UUCP>
Organization: Sugar Land Unix - Houston, TX
Lines: 14

In article <3750@ece-csc.UUCP>, rss@ece-csc.UUCP (ML) writes:
> seem to.  (This applies only to line buffered streams, i.e., stdout).
> "Stderr" should be completely unbuffered...

Even better would be to adopt the Berkeley stdio convention, and have
filbuf on an interactive stream do a flush on all interactive output
streams. That way you get the correct result when you print a prompt,
and you don't have an extra check on every character output.

Stderr should, indeed, be unbuffered. Or at least it should flush after
every call to stdio.
-- 
		Peter da Silva  `-_-'  peter@sugar.uu.net
		 Have you hugged  U  your wolf today?