Re^4: WIN redirecting STDOUT and STDIN to new spawned CMD console


There's more than one way to do things
	PerlMonks

Re^4: WIN redirecting STDOUT and STDIN to new spawned CMD console

by soonix (Canon)

on Mar 29, 2023 at 08:19 UTC ( [id://11151315]=note: print w/replies, xml )

Need Help??

in reply to Re^3: WIN redirecting STDOUT and STDIN to new spawned CMD console
in thread WIN redirecting STDOUT and STDIN to new spawned CMD console

I'm only half (or even less) certain that I already used named pipes on Windows, but both MS and SO say that it's possible.

Comment on Re^4: WIN redirecting STDOUT and STDIN to new spawned CMD console

Replies are listed 'Best First'.

Re^5: WIN redirecting STDOUT and STDIN to new spawned CMD console
by bliako (Monsignor) on Mar 29, 2023 at 10:35 UTC

Also, https://rkeithhill.wordpress.com/2014/11/01/windows-powershell-and-named-pipes/ one of many links showing how to create them pipes in powershell. Oh you need to ignite the pipe server! I can't believe it's not butter lol. And lol2 reading the comments under SO links provided above, like: A|B|C is possible but it waits A to finish in order to "pipe" its output into B and ditto on to C. I stop here lest this becomes trolling.

Q: can IPC::Run be used to create windows pipes? LIMITATIONS section says it's experimental.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom