home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!world!jrs
- From: jrs@world.std.com (Rick Sladkey)
- Subject: Re: Good comm program?
- In-Reply-To: hlu@phys1.physics.wsu.edu's message of 21 Jul 92 23:50:57 GMT
- Message-ID: <JRS.92Jul22203246@lepton.world.std.com>
- Lines: 19
- Sender: jrs@world.std.com (Rick Sladkey)
- Organization: The World
- References: <arumble.711622204@extro.ucc.su.OZ.AU>
- <9207201343@myamig2.myamiga.mixcom.com>
- <1992Jul21.235057.14132@serval.net.wsu.edu>
- Date: Thu, 23 Jul 1992 00:32:46 GMT
-
- >>>>> On 21 Jul 92 23:50:57 GMT, hlu@phys1.physics.wsu.edu (Hongjiu Lu) said:
-
- H.J.> If you use stdio, I believe everything is buffered by default.
-
- The defaults for Unix since K&R are:
-
- * stdin and stdout to a terminal/pty are line-buffered
-
- * stdin and stdout to a file or pipe are block-buffered
-
- * stderr is alway unbuffered
-
- * a read from a terminal/pty causes a flush of any output to the same device
-
- Earlier versions of iostream had various discrepencies with this scheme
- but iostream for GCC 2.2.2 now follows these conventions.
- --
- Rick Sladkey
- jrs@world.std.com
-