Re: Bug#155536: ITP: pip -- make any program a filter

[Helios de Creisquer <creis@tuxfamily.org>]

On Mon, Aug 05, 2002 at 06:13:01PM +0000, Miquel van Smoorenburg wrote:
> In article <[🔎] 87k7n5b2se.fsf@kali.chezwam.org>,
> Sebastien J. Gross  <sjg@debian.org> wrote:
> >Josselin Mouette <josselin.mouette@ens-lyon.org> writes:
> >
> >Yes in some case you need a pipe-like command.
> >Using std(in|out) does not allow you to pipe any data to a program.
> program1 | exoticprog --infile /dev/stdin --outfile /dev/stdout | program2
> >Pip allow users to do that.
> So does /dev/stdin and /dev/stdout

Seen on the homepage of pip:

###
Pip versus /dev/stdin and /dev/stdout

On most Unices, you can often get  the  same  effect  as  pip  by  using
/dev/stdin and /dev/stdout (thanks to Daniel Biddle  for  pointing  this
out). However although this works for  programs  which  read  and  write
sequentially,  and  gets  you  the  normal  pipeline  laziness  in  such
situations, it won't work for those that want to do  random-access  file
operations on their input or output.
###

so pip allows to do random access on stdin/stdout... Is  the  /dev/stdin
and /dev/stdout solution allows that ?

-- 
Helios de Creisquer <helios@balios.org>