In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/4642e50d936f507ad436fe48093d9efae111f983?hp=9590a7cd37f06922f07d87081a2fdf6a96c22b56>
- Log ----------------------------------------------------------------- commit 4642e50d936f507ad436fe48093d9efae111f983 Author: Eric Brine <[email protected]> Date: Fri Mar 2 18:47:39 2012 -0800 fix documentation for exec's warning behavior This should self-consistently and correctly identify when exec will warn. [ commit message rewritten by rjbs ] ----------------------------------------------------------------------- Summary of changes: pod/perlfunc.pod | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 4fd0a3a..08db117 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -1944,10 +1944,10 @@ returns false only if the command does not exist I<and> it is executed directly instead of via your system's command shell (see below). Since it's a common mistake to use C<exec> instead of C<system>, Perl -warns you if there is a following statement that isn't C<die>, C<warn>, -or C<exit> (if C<-w> is set--but you always do that, right?). If you -I<really> want to follow an C<exec> with some other statement, you -can use one of these styles to avoid the warning: +warns you if C<exec> is called in void context and if there is a following +statement that isn't C<die>, C<warn>, or C<exit> (if C<-w> is set--but +you always do that, right?). If you I<really> want to follow an C<exec> +with some other statement, you can use one of these styles to avoid the warning: exec ('foo') or print STDERR "couldn't exec foo: $!"; { exec ('foo') }; print STDERR "couldn't exec foo: $!"; -- Perl5 Master Repository
