summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2011-12-26 14:17:03 -0800
committerFather Chrysostomos <sprout@cpan.org>2011-12-26 14:17:03 -0800
commitf8c3fed4ccf90f2b41f9acc87c1b11359f095598 (patch)
tree3bc813a0b123c3322db95d25e8b019a05fab6894
parent770a14974fdbbc4f0df0c34be75556909a491dfd (diff)
downloadperl-f8c3fed4ccf90f2b41f9acc87c1b11359f095598.tar.gz
Consistent use of spaces after dots in diagnostics.pm
-rw-r--r--lib/diagnostics.pm7
1 files changed, 4 insertions, 3 deletions
diff --git a/lib/diagnostics.pm b/lib/diagnostics.pm
index b1456bb678..dc1a9b0f39 100644
--- a/lib/diagnostics.pm
+++ b/lib/diagnostics.pm
@@ -59,13 +59,14 @@ descriptions). User code generated warnings a la warn() are unaffected,
allowing duplicate user messages to be displayed.
This module also adds a stack trace to the error message when perl dies.
-This is useful for pinpointing what caused the death. The B<-traceonly> (or
+This is useful for pinpointing what
+caused the death. The B<-traceonly> (or
just B<-t>) flag turns off the explanations of warning messages leaving just
-the stack traces. So if your script is dieing, run it again with
+the stack traces. So if your script is dieing, run it again with
perl -Mdiagnostics=-traceonly my_bad_script
-to see the call stack at the time of death. By supplying the B<-warntrace>
+to see the call stack at the time of death. By supplying the B<-warntrace>
(or just B<-w>) flag, any warnings emitted will also come with a stack
trace.