This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: Fwd: Bug#43023: libc 2.1.1-10 makes it impossible to use stdoutreliably
- To: Joel Klecker <jk@espy.org>
- Subject: Re: Fwd: Bug#43023: libc 2.1.1-10 makes it impossible to use stdoutreliably
- From: Alex Buell <alex.buell@tahallah.demon.co.uk>
- Date: Sun, 15 Aug 1999 21:46:40 +0100 (BST)
- cc: libc-alpha@sourceware.cygnus.com
- Reply-To: alex.buell@tahallah.demon.co.uk
On Sun, 15 Aug 1999, Joel Klecker wrote:
> However, stdio buffers things. In many cases, the data doesn't get
> written until the program returns from main or calls exit(3).
> Furthermore there exist a number of network filesystems and similar
> systems where write errors are not reported until close(2). So a
> straightforward `hello world' program, for example, might well lose
> data, even if it checked the return from printf(3).
BOLLOCKS, COMPLETE BOLLOCKS. Three choices: 1) Don't use stdio 2) turn
buffering off 3) use fflush(). Read the info files for further
information.
*plonk*
I don't like trolls.
Cheers,
Alex
--
Legalise cannabis today!
http://www.tahallah.demon.co.uk