Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: stream buffering

X-seq: zsh-users 15811
From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
To: zsh-users@xxxxxxx
Subject: Re: stream buffering
Date: Fri, 18 Feb 2011 20:55:51 +0000
In-reply-to: <alpine.DEB.2.02.1102171938510.16574@MyComp2.rgm-web.net>
List-help: <mailto:zsh-users-help@zsh.org>
List-id: Zsh Users List <zsh-users.zsh.org>
List-post: <mailto:zsh-users@zsh.org>
Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
References: <alpine.DEB.2.02.1102171938510.16574@MyComp2.rgm-web.net>

On Thu, 17 Feb 2011 19:40:20 -0600 (CST)
Rory Mulvaney <rorymulv@xxxxxxxxx> wrote:
> I'm wondering if the reason that some I/O intensive zsh shell scripts 
> aren't fast is mostly only because the I/O is (I think) line-buffered. 
> Is there a way to do full buffering of streams, or what would be the best 
> way to provide it?  Maybe a module similar to zsh/net/socket, perhaps 
> using setvbuf(3)?

What I/O are you referring to?  The shell's own input for a script needs
to be parsed and intepreted, which will be much more of a restriction
than buffering except for scripts with really silly amounts of embedded
text like here documents.  Standard input to the shell via the read
builtin etc. similarly tends to be in short chunks, likewise output via
print.  Input to other commands run from scripts makes its own
arrangements for buffering.

-- 
Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/

References:
- stream buffering
  - From: Rory Mulvaney

Messages sorted by: Reverse Date, Date, Thread, Author