[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sed bug on seekable stdin
From: |
Eric Blake |
Subject: |
Re: sed bug on seekable stdin |
Date: |
Mon, 18 Dec 2006 19:14:21 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Paul Eggert <eggert <at> CS.UCLA.EDU> writes:
>
> Andreas Schwab <schwab <at> suse.de> writes:
>
> > fflush on an input stream has undefined behaviour.
>
> This is true in some versions of POSIX but not others. It is a
> contentious and murky area. If memory serves, fflushing an input
> stream had defined behavior in POSIX 1988, then it became undefined,
> and now (or soon?) it is becoming defined again.
Indeed, based on this statement, I revisited the Austin Group publications, and
came across these links, which do indeed specify fflush() on read streams:
http://www.opengroup.org/austin/interps/uploads/40/6806/AI-002.txt
http://www.opengroup.org/austin/interps/uploads/40/9984/AI-085.txt
With that ammunition, I reopened glibc bug 3746, with the hope that Ulrich will
concede to the standards or offer a better excuse other than just accusing me
of pushing my problems off to glibc.
http://sources.redhat.com/bugzilla/show_bug.cgi?id=3746
In the meantime, there are several released versions of glibc that have this
bug on seekable stdin, so it is still worth considering gnulib improvements
that might make it easier for gnulib clients to work around it.
--
Eric Blake
- Re: sed bug on seekable stdin, (continued)
- Re: sed bug on seekable stdin, Eric Blake, 2006/12/17
- Re: sed bug on seekable stdin, Andreas Schwab, 2006/12/17
- Re: sed bug on seekable stdin, Eric Blake, 2006/12/17
- Re: sed bug on seekable stdin, Paul Jarc, 2006/12/17
- Re: sed bug on seekable stdin, Paul Eggert, 2006/12/18
- Re: sed bug on seekable stdin,
Eric Blake <=
Re: sed bug on seekable stdin, Paolo Bonzini, 2006/12/18