diff options
author | Jesse Vincent <jesse@bestpractical.com> | 2009-08-03 12:06:00 +0100 |
---|---|---|
committer | Jesse Vincent <jesse@bestpractical.com> | 2009-08-03 12:09:17 +0100 |
commit | 1af1c0d6fc56624ceeee486b9d34f20643ac0ecd (patch) | |
tree | 3fb098bd080583765f6856e4d79550ffb8066cdd | |
parent | 1841b798695a5565093e45ec6949bf34b1601dfe (diff) | |
download | perl-1af1c0d6fc56624ceeee486b9d34f20643ac0ecd.tar.gz |
Update the description of the 'system' function to point users at autodie
pjf++ for complaining about the POD for system during his Klingon
Programming talk at YAPC::EU 2009
-rw-r--r-- | pod/perlfunc.pod | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 3a345aa2f4..9f95bb04cf 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -6474,6 +6474,9 @@ C<qx//>, as described in L<perlop/"`STRING`">. Return value of -1 indicates a failure to start the program or an error of the wait(2) system call (inspect $! for the reason). +If you'd like to make C<system> (and many other bits of Perl) die on error, +have a look at the L<autodie> pragma. + Like C<exec>, C<system> allows you to lie to a program about its name if you use the C<system PROGRAM LIST> syntax. Again, see L</exec>. @@ -6486,8 +6489,8 @@ value. system(@args) == 0 or die "system @args failed: $?" -You can check all the failure possibilities by inspecting -C<$?> like this: +If you'd like to manually inspect C<system>'s failure, u can check all +possible failure modes by inspecting C<$?> like this: if ($? == -1) { print "failed to execute: $!\n"; |