Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!rpi!image.soe.clarkson.edu!news From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.sources.games.bugs Subject: Re: What setbuf() is and why you should use it Message-ID: Date: 16 Jul 89 01:48:43 GMT References: <283@wet.UUCP> Sender: news@sun.soe.clarkson.edu Reply-To: nelson@clutx.clarkson.edu Followup-To: comp.sources.games.bugs Organization: Clarkson University, Postdam NY Lines: 16 In-reply-to: epsilon@wet.UUCP's message of 15 Jul 89 22:28:12 GMT In article <283@wet.UUCP> epsilon@wet.UUCP (Eric P. Scott) writes: Many, many screen-oriented applications posted to the net have a serious flaw: they do terminal output a character at a time. This is fine for single-user PCs running MSDOS. ... No it isn't. "Kernel"[1] calls in MS-LOSS have quite a big of overhead, and the difference between buffered and unbuffered I/O *is* noticable. So please, use setbuf in your MS-LOSS programs also. [1] To the extent that MS-LOSS can be said to have a kernel. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) I'm not the NRA, and I vote twice.