Article View: comp.sys.amiga.tech
Article #9465Re: Lattice C 4.0 bugs
From: Peter da Silva
Date: Fri, 12 Aug 1988 16:27
Date: Fri, 12 Aug 1988 16:27
14 lines
1093 bytes
1093 bytes
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?
Technical Details
Message-ID:
<2458@sugar.uu.net>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!attcan!uunet!husc6!rutgers!bellcore!tness7!tness1!sugar!peterReferences:
<6627@bloom-beacon.MIT.EDU> <3750@ece-csc.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!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