perlfaq8: Why doesn't open() return an error when a pipe open fails?
[email protected] (_brian_d_foy)
| Newsgroups | perl.perlfaq.workers,perl.documentation |
|---|---|
| Message-ID | <041120021503426729%[email protected]> |
* minor corrections for consistent style Index: perlfaq8.pod =================================================================== RCS file: /cvs/public/perlfaq/perlfaq8.pod,v retrieving revision 1.13 diff -u -d -r1.13 perlfaq8.pod --- perlfaq8.pod 8 Oct 2002 08:06:40 -0000 1.13 +++ perlfaq8.pod 4 Nov 2002 21:01:46 -0000 @@ -763,7 +763,7 @@ =head2 Why doesn't open() return an error when a pipe open fails? -If the second argument to a piped C<open> contains shell +If the second argument to a piped open() contains shell metacharacters, perl fork()s, then exec()s a shell to decode the metacharacters and eventually run the desired program. If the program couldn't be run, it's the shell that gets the message, not Perl. All @@ -771,9 +771,9 @@ successfully started. You can still capture the shell's STDERR and check it for error messages. See L<"How can I capture STDERR from an external command?"> elsewhere in this document, or use the -L<IPC::Open3> module. +IPC::Open3 module. -If there are no shell metacharacters in the argument of C<open>, Perl +If there are no shell metacharacters in the argument of open(), Perl runs the command directly, without using the shell, and can correctly report whether the command started. g