summaryrefslogtreecommitdiff
path: root/pod/perlipc.pod
diff options
context:
space:
mode:
authorbrian d foy <bdfoy@cpan.org>2010-01-13 17:19:25 +0100
committerbrian d foy <bdfoy@cpan.org>2010-01-13 17:19:25 +0100
commitac0367249e563330db9a9a04f778eae30defbab0 (patch)
tree7f99b67d93a06be0fb7aa702db8dfd4e24ff501d /pod/perlipc.pod
parent8d2e243f5816f9d2c4247f962523e4220e4a9ce8 (diff)
downloadperl-ac0367249e563330db9a9a04f778eae30defbab0.tar.gz
* Em dash cleanup in pod/
I looked at all the instances of spaces around -- and in most cases converted the sentences to use more appropriate punctuation. In general, the -- in the perl docs seem to be there only to make really complicated and really long sentences. I didn't look at the closed em-dashes. They probably have the same sentence-complexity problem. I left some open em-dashes in place. Those are the ones used in lists.
Diffstat (limited to 'pod/perlipc.pod')
-rw-r--r--pod/perlipc.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlipc.pod b/pod/perlipc.pod
index 25b310bb7b..4f6c0f0484 100644
--- a/pod/perlipc.pod
+++ b/pod/perlipc.pod
@@ -316,8 +316,8 @@ The pragmatic approach was to say "I know the risks, but prefer the
convenience", and to do anything you wanted in your signal handler,
and be prepared to clean up core dumps now and again.
-In Perl 5.7.3 and later to avoid these problems signals are
-"deferred"-- that is when the signal is delivered to the process by
+Perl 5.7.3 and later avoid these problems by "deferring" signals.
+That is, when the signal is delivered to the process by
the system (to the C code that implements Perl) a flag is set, and the
handler returns immediately. Then at strategic "safe" points in the
Perl interpreter (e.g. when it is about to execute a new opcode) the