Clear questions and runnable code
get the best and fastest answer
It's using lexicals that causes problems. This module predates lexicals.
13 years on and it doesn't support lexicals. is 'Broken by Design'.
And even if you use globs, there is no sensible way to use the 3 handle version on windows because select doesn't work on file handles.
Even the documentation is sorely lacking.
At the very least there should be a big, clear warning "Doesn't work with lexicals" in the warnings section. The bland parenthetical "(this means that an autovivified lexical cannot be used for the STDERR filehandle, see SYNOPSIS)" is hardly adequate given the nature of the limitation and the module's raison d'etre.
The discussion regarding the likelihood of deadlocking when trying to process two concurrent asynchronous streams is also woefully inadequate.
The modules place in the core and frequent recommendations, bely the difficulty of its practical use; which is further compounded by the lack of discussion of those difficulties, and examples of working around them.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In reply to Re^4: Is there a problem with IPC::Open on Windows 7?