From: Jilles Tjoelker <jilles@stack.nl>
To: Steve Schnepp <steve.schnepp@gmail.com>
Cc: dash@vger.kernel.org, 595063@bugs.debian.org
Subject: Re: read() builtin doesn't read integer value /proc files (but bash's does)
Date: Fri, 3 Sep 2010 23:25:05 +0200 [thread overview]
Message-ID: <20100903212504.GA86276@stack.nl> (raw)
In-Reply-To: <AANLkTi=ZcNYJKCO_FM0RpJndwAgtzTU_C8J=9BsfmdAk@mail.gmail.com>
On Thu, Sep 02, 2010 at 05:02:55PM +0200, Steve Schnepp wrote:
> 2010/9/1 Steve Schnepp <steve.schnepp@gmail.com>:
> > conforming to POSIX isn't a realistic option, would it be possible to
> > have a workaround that doesn't involve an external tool like cat(1) ?
> Hi, I just hacked & attached a little patch away to be able to solve
> this case.
> Feel free to reply with your comments.
> NB: I just targeted dash-0.5.5.1, but it might apply to any version.
This patch assumes that the file descriptor is discarded afterwards (its
position does not matter). Therefore the very common construct
while read x; do
...
done
stops working.
A possible fix is to check first if the input supports seeking. If it
does, use the buffering and at the end of the line seek backwards for
the number of bytes remaining in the buffer. If it does not, read one
byte at a time.
--
Jilles Tjoelker
next prev parent reply other threads:[~2010-09-03 21:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 8:10 read() builtin doesn't read integer value /proc files (but bash's does) Steve Schnepp
2010-09-02 15:02 ` Steve Schnepp
2010-09-03 21:25 ` Jilles Tjoelker [this message]
2010-09-04 18:20 ` Steve Schnepp
2010-09-04 19:35 ` Jilles Tjoelker
2010-11-28 8:42 ` Herbert Xu
2010-12-15 9:49 ` read() builtin doesnt read integer value /proc files (but bashs does) Cristian Ionescu-Idbohrn
2010-12-15 18:55 ` Jonathan Nieder
2010-12-15 19:12 ` Cristian Ionescu-Idbohrn
2010-12-18 22:23 ` Jilles Tjoelker
2010-09-02 19:09 ` read() builtin doesn't read integer value /proc files (but bash's does) Jilles Tjoelker
2010-09-03 9:23 ` Steve Schnepp
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=20100903212504.GA86276@stack.nl \
--to=jilles@stack.nl \
--cc=595063@bugs.debian.org \
--cc=dash@vger.kernel.org \
--cc=steve.schnepp@gmail.com \
/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