summaryrefslogtreecommitdiff
path: root/pod/perldata.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/perldata.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/perldata.pod')
-rw-r--r--pod/perldata.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/pod/perldata.pod b/pod/perldata.pod
index 3c1a95e2c4..bc564e650d 100644
--- a/pod/perldata.pod
+++ b/pod/perldata.pod
@@ -633,9 +633,9 @@ key/value pairs. That's why it's good to use references sometimes.
It is often more readable to use the C<< => >> operator between key/value
pairs. The C<< => >> operator is mostly just a more visually distinctive
synonym for a comma, but it also arranges for its left-hand operand to be
-interpreted as a string -- if it's a bareword that would be a legal simple
-identifier (C<< => >> doesn't quote compound identifiers, that contain
-double colons). This makes it nice for initializing hashes:
+interpreted as a string if it's a bareword that would be a legal simple
+identifier. C<< => >> doesn't quote compound identifiers, that contain
+double colons. This makes it nice for initializing hashes:
%map = (
red => 0x00f,