in reply to Re^2: Can't close pipe to invalid process
in thread Can't close pipe to invalid process
It was the not finding "prince" that caused it to fail (pretty much what aitap said).
Intuitively, I would think the open should fail if the executable being piped to can't be found, but that wasn't the case.
I added a test for the print, and that appears to return true.
So, what I have is:
ok 3 - Opened pipe ok 4 - Piped content to prince not ok 5 - Closed pipe
I'm wondering if an assumption is made internally about piping to the executable until Perl receives a return value on closing?!?
In Section
Seekers of Perl Wisdom