From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sed oddity
Date: Wed, 19 Aug 2009 09:47:14 +0200 [thread overview]
Message-ID: <138575260908190047o220ee1dfv2b0675cfb0b51526@mail.gmail.com> (raw)
In-Reply-To: <5c343887249a3ffa3bab09d34d26b3a4@quanstro.net>
Sadly things like sed are out of my reach; I have no idea how to
program languages.
Thanks for the reply.
2009/8/18, 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
>
>
--
Hugo
prev parent reply other threads:[~2009-08-19 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 14:41 hugo rivera
2009-08-18 14:55 ` Uriel
2009-08-18 15:25 ` Gorka Guardiola
2009-08-18 16:00 ` roger peppe
2009-08-19 10:35 ` Uriel
2009-08-18 15:38 ` erik quanstrom
2009-08-19 7:47 ` hugo rivera [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=138575260908190047o220ee1dfv2b0675cfb0b51526@mail.gmail.com \
--to=uair00@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).