diff options
Diffstat (limited to 'pod/modpods/Open2.pod')
| -rw-r--r-- | pod/modpods/Open2.pod | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/pod/modpods/Open2.pod b/pod/modpods/Open2.pod index 19f0369cfd..942f68446d 100644 --- a/pod/modpods/Open2.pod +++ b/pod/modpods/Open2.pod @@ -30,4 +30,14 @@ It assumes it's going to talk to something like B<bc>, both writing to it and reading from it. This is presumably safe because you "know" that commands like B<bc> will read a line at a time and output a line at a time. Programs like B<sort> that read their entire input stream first, -however, are quite apt to cause deadlock. See L<open3> for an alternative. +however, are quite apt to cause deadlock. + +The big problem with this approach is that if you don't have control +over source code being run in the the child process, you can't control what it does +with pipe buffering. Thus you can't just open a pipe to "cat -v" and continually +read and write a line from it. + +=head1 SEE ALSO + +See L<open3> for an alternative that handles STDERR as well. + |