summaryrefslogtreecommitdiff
path: root/pod/perlfunc.pod
diff options
context:
space:
mode:
authorNiko Tyni <ntyni@debian.org>2008-05-18 00:37:30 +0300
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2008-05-18 06:28:49 +0000
commit5f1da31cc3010163aa29135d0c83706ab31118b8 (patch)
treeca71a5e0e7c45295092ccb0e06a68ac9618b2cf2 /pod/perlfunc.pod
parent09782346ff1f47d913bef106d29466f3d41825c8 (diff)
downloadperl-5f1da31cc3010163aa29135d0c83706ab31118b8.tar.gz
Re: eval "require Foo" with binary-incompatible XS modules
Message-ID: <20080517183730.GA4440@rebekka> p4raw-id: //depot/perl@33848
Diffstat (limited to 'pod/perlfunc.pod')
-rw-r--r--pod/perlfunc.pod4
1 files changed, 4 insertions, 0 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 764deb07a5..864699d98b 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -1562,6 +1562,10 @@ determining whether a particular feature (such as C<socket> or C<symlink>)
is implemented. It is also Perl's exception trapping mechanism, where
the die operator is used to raise exceptions.
+If you want to trap errors when loading an XS module, some problems with
+the binary interface (such as Perl version skew) may be fatal even with
+C<eval> unless C<$ENV{PERL_DL_NONLAZY}> is set. See L<perlrun>.
+
If the code to be executed doesn't vary, you may use the eval-BLOCK
form to trap run-time errors without incurring the penalty of
recompiling each time. The error, if any, is still returned in C<$@>.