-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bruno Haible on 9/26/2008 8:10 AM: >> I know this condition arises only when ignoring or handling SIGPIPE, >> (which should be rather unusual) but even so, I really dislike the idea >> of ignoring a write error. Even if the write error would not occur >> with slightly less output data, it's still one less _legitimate_ error >> that can be reported. If there is an EPIPE error, IMHO, close_stream >> must diagnose it. > > This does not convince me, because EPIPE is part of the normal shutdown > protocol of pipes, when the pipe writer chooses to block or ignore SIGPIPE. > > The very purpose of having different error codes listed in <errno.h> is > to be able to react differently on them.
Sounds like we should ask the Austin group for an opinion. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjgwk4ACgkQ84KuGfSFAYA2HgCfX7wO58HIN/+BFnncLKaxmqpu raYAnj/KwGfM00iaY36Mb9fQZro78KAc =iqI7 -----END PGP SIGNATURE-----
