From: Abigail <abigail@abigail.be>
Date: Wed, 23 Jan 2002 15:35:47 +0000 (+0100)
Subject: Re: eval not catching warnings?
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=d9984052ba632ec50d14b1afa97960143b6781f2;p=p5sagit%2Fp5-mst-13.2.git

Re: eval not catching warnings?
Message-ID: <20020123143547.24798.qmail@foad.org>

p4raw-id: //depot/perl@14384
---

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 8fcc060..8efe7cc 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -1336,8 +1336,9 @@ executed, an undefined value is returned by C<eval>, and C<$@> is set to the
 error message.  If there was no error, C<$@> is guaranteed to be a null
 string.  Beware that using C<eval> neither silences perl from printing
 warnings to STDERR, nor does it stuff the text of warning messages into C<$@>.
-To do either of those, you have to use the C<$SIG{__WARN__}> facility.  See
-L</warn> and L<perlvar>.
+To do either of those, you have to use the C<$SIG{__WARN__}> facility, or
+turn off warnings inside the BLOCK or EXPR using S<C<no warnings 'all'>>.
+See L</warn>, L<perlvar>, L<warnings> and L<perllexwarn>.
 
 Note that, because C<eval> traps otherwise-fatal errors, it is useful for
 determining whether a particular feature (such as C<socket> or C<symlink>)