Re: sed bug on seekable stdin

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Bob Proulx on 12/17/2006 1:14 PM:
> The original motivation was Eric's posting reporting a portability
> problem and POSIX non-compliance issue.  Here is the original message
> in the archive.
> 
>   http://lists.gnu.org/archive/html/bug-gnu-utils/2006-12/msg00059.html

See also Ralf Wildenhues' report of an M4 testsuite failure caused by the
incorrect behavior of sed on Linux, the thread that sparked this bug report:
http://lists.gnu.org/archive/html/bug-m4/2006-12/msg00012.html

> 
> While on GNU based systems no output is emitted.  (I peeked at Debian,
> Ubuntu, RHEL and SLES.)  These systems violate POSIX and differ from
> traditional Unix behavior.

Which is why I was very disappointed at Ulrich's decision that glibc is
not going to change to be compatible with everyone else:
http://sources.redhat.com/bugzilla/show_bug.cgi?id=3746

In my opinion, it would be much easier to fix exit() in glibc once than to
force an audit of all utilities, including sed, to make them add a fix to
explicitly close stdin.

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFhcWT84KuGfSFAYARAkxVAJ92q/m/J7LtVfzn4/KtXCeUK4gh5wCfYAyR
MyEkTd5cDxXef4Yk9vGKRLM=
=jKvO
-----END PGP SIGNATURE-----