From 4642e50d936f507ad436fe48093d9efae111f983 Mon Sep 17 00:00:00 2001 From: Eric Brine Date: Fri, 2 Mar 2012 18:47:39 -0800 Subject: [PATCH] fix documentation for exec's warning behavior This should self-consistently and correctly identify when exec will warn. [ commit message rewritten by rjbs ] --- pod/perlfunc.pod | 8 ++++---- 1 file 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 it is executed directly instead of via your system's command shell (see below). Since it's a common mistake to use C instead of C, Perl -warns you if there is a following statement that isn't C, C, -or C (if C<-w> is set--but you always do that, right?). If you -I want to follow an C with some other statement, you -can use one of these styles to avoid the warning: +warns you if C is called in void context and if there is a following +statement that isn't C, C, or C (if C<-w> is set--but +you always do that, right?). If you I want to follow an C +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: $!"; -- 1.8.3.1