Dnia 10 Feb 2006 06:11:57 -0800, Arjen Markus skrobie:
I'm gonna experiment, but only when there is some reasonable solution. This
one you gave here is good, but not perfect. If my script has to be occupied
with redirecting pipe's channels to natural std* channels, there has to be
also some means to make a difference between stdout and stderr. If I open one
pipe for both reading and writing, I must know, what channel was some text
I'd like to have a generic solution. If I use it, for example, inside my
script to produce some results that will be redirected from stdout, I need
that the text written to stderr (by the underling process) be filtered out.
// _ ___ Michal "Sektor" Malecki <sektor(whirl)kis.p.lodz.pl>
\\ L_ |/ `| /^\ ,() <ethourhs(O)wp.pl>
// \_ |\ \/ \_/ /\ C++ bez cholesterolu: http://www.yqcomputer.com/
"I am allergic to Java because programming in Java reminds me casting spells"