summaryrefslogtreecommitdiff
path: root/pod/perlcall.pod
diff options
context:
space:
mode:
authorHugo van der Sanden <hv@crypt.org>1998-07-27 15:34:45 +0200
committerGurusamy Sarathy <gsar@cpan.org>1998-08-02 03:33:07 +0000
commit268118b230b225b283ec54291ec9a46f100cfddc (patch)
treea1fc21e594bfff4bcba9cc12d15cecd7debc9cf7 /pod/perlcall.pod
parent2b2708c8874957427cdc4340c4d482c88a9aef90 (diff)
downloadperl-268118b230b225b283ec54291ec9a46f100cfddc.tar.gz
perlcall.pod
Message-Id: <199807271134.NAA24475@dorlas.elsevier.nl> p4raw-id: //depot/maint-5.005/perl@1680
Diffstat (limited to 'pod/perlcall.pod')
-rw-r--r--pod/perlcall.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlcall.pod b/pod/perlcall.pod
index 7c94d377c7..c239cfe324 100644
--- a/pod/perlcall.pod
+++ b/pod/perlcall.pod
@@ -279,8 +279,8 @@ belongs to C<joe>.
It is possible for the Perl subroutine you are calling to terminate
abnormally, e.g., by calling I<die> explicitly or by not actually
-existing. By default, when either of these of events occurs, the
-process will terminate immediately. If though, you want to trap this
+existing. By default, when either of these events occurs, the
+process will terminate immediately. If you want to trap this
type of event, specify the G_EVAL flag. It will put an I<eval { }>
around the subroutine call.