diff options
| author | brian d foy <bdfoy@cpan.org> | 2010-01-13 17:19:25 +0100 |
|---|---|---|
| committer | brian d foy <bdfoy@cpan.org> | 2010-01-13 17:19:25 +0100 |
| commit | ac0367249e563330db9a9a04f778eae30defbab0 (patch) | |
| tree | 7f99b67d93a06be0fb7aa702db8dfd4e24ff501d /pod/perlxstut.pod | |
| parent | 8d2e243f5816f9d2c4247f962523e4220e4a9ce8 (diff) | |
| download | perl-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/perlxstut.pod')
| -rw-r--r-- | pod/perlxstut.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod index 090b14a9e7..62bef3b0c5 100644 --- a/pod/perlxstut.pod +++ b/pod/perlxstut.pod @@ -865,7 +865,7 @@ However, to help ease understanding, it is suggested that you place a "&" next to the variable name and away from the variable type), and place a "*" near the variable type, but away from the variable name (as in the call to foo above). By doing so, it is easy to understand exactly what -will be passed to the C function -- it will be whatever is in the "last +will be passed to the C function; it will be whatever is in the "last column". You should take great pains to try to pass the function the type of variable |