Re: [9fans] sed oddity

[erik quanstrom <quanstro@quanstro.net>]

> is there some reason why sed doesn't check for write errors on its
> stdout? (or at least it doesn't report them)

/n/sources/patch/sederrors

while i agree that sed seems more complicated that i would
like when debugging, eating errors seems like the wrong thing
to do.  it seems easy enough >[2]/dev/null if the old behavior
is wanted.

the problem was that B* functions (Bopen, Bputc, Bputrune, Bterm)
were not consistently being checked for errors.

i wonder if it would make sense to add a ->error() member
to Biobufhdr.  since most programs just want to quit if they
have a bio error, they could just quit there without needing
lots tedious error checking.

perhaps ->error could just be a boolean.

- erik