This is a live mirror of the Perl 5 development currently hosted at
https://github.com/perl/perl5
https://perl5.git.perl.org
/
perl5.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
7fa7b0a
)
Fix 2 pod errors in perlvms.pod.
author
Craig A. Berry
<craigberry@mac.com>
Thu, 15 Oct 2009 16:01:33 +0000
(11:01 -0500)
committer
Craig A. Berry
<craigberry@mac.com>
Thu, 15 Oct 2009 16:01:33 +0000
(11:01 -0500)
pod/perlvms.pod
patch
|
blob
|
blame
|
history
diff --git
a/pod/perlvms.pod
b/pod/perlvms.pod
index
9854ff8
..
d7ed2bc
100644
(file)
--- a/
pod/perlvms.pod
+++ b/
pod/perlvms.pod
@@
-772,7
+772,7
@@
true, a warning message is printed, and C<undef> is returned.
=item kill
In most cases, C<kill> is implemented via the undocumented system
-service
<$SIGPRC>, which has the same calling sequence as
<$FORCEX>, but
+service
C<$SIGPRC>, which has the same calling sequence as C
<$FORCEX>, but
throws an exception in the target process rather than forcing it to call
C<$EXIT>. Generally speaking, C<kill> follows the behavior of the
CRTL's C<kill()> function, but unlike that function can be called from