You know nothing about Unix or computers, Filipe.
stdin is a named pipe. Standard IO. Input/output.
What comes in goes out. Same as life and this  bull you are saying.

----- Original Message ----- 
From: "Felipe Sateler" 
To: "Michael Gogins" ; "Developer discussions" 

Sent: Sunday, July 06, 2008 9:47 PM
Subject: Re: [Cs-dev] Csound output


> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08


--------------------------------------------------------------------------------


> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Steven Yi wrote:
> I beg to differ, Felipe knows a great deal about computers and *nix,
> and is also the maintainer of the Csound Debian packages and is pretty
> well respected around here.
> 
> Also, stdin/stdout are not named pipes.
> 

Indeed - they are not pipes at all. They are sources and a destination 
("streams" in modern parlance) for data that could be sent, OS 
permitting, through a pipe. Early generations of unix audio tools (such 
as the CARL distribution) tended to write audio data to stdout as 
(usually) text floatsams, and read audio input likewise through stdin, 
relying on the unix pipe infrastructure to create chains of processes 
the final destination of which would be a file of some sort. In such a 
situation, of course, all informative text output has to be routed 
separately from the audio stream, hence the use of stderr.

Richard Dobson



-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net