> > > So are you saying that IPC::Open3 *can* do piped commands,
> > > but just that
> > > it isn't very nice behind the scenes?
> >
> > not only performance.
> >
> > It starts $^X as subprocess whith some parameters to manage
> Win32 pipes and
> > assumes that it starts another instance of Perl (or two) to
> help processing.
> > This fails miserably and silently when invoked from
> application, which
> > embeds perl, where $^X is something else. It just dont work
> and no warning
> > during execution or mentioning of such a limitation.
> >
> > I don't know how to fix this however.
>
> I couldn't find the literal text $^X in Open3.pm, so I'm not
> sure where the
> buggy code is. What did I miss?
that is inside IPC::Run, which uses IPC::Run::Win32IO on win32 to do pipes
work, and it suffers this behaviour.
This closely relates in general, but probably does not fit to current
discussion.
Sorry, this probably should be in different topic..
Vadim.