summaryrefslogtreecommitdiff
path: root/pod/perlhack.pod
diff options
context:
space:
mode:
authorStas Bekman <stas@stason.org>2002-04-23 09:59:07 +0800
committerAbhijit Menon-Sen <ams@wiw.org>2002-04-22 18:10:13 +0000
commit884bad00cca84e3362ce7b5e71a81555b48ce98b (patch)
tree5f1ca7d1b525d0f57bfc1e41be6b94f3a9830f24 /pod/perlhack.pod
parent1b2e2dfb878b94f2cea3d118c3393e34d3e69682 (diff)
downloadperl-884bad00cca84e3362ce7b5e71a81555b48ce98b.tar.gz
small corrections
Message-Id: <3CC44F6B.5010300@stason.org> p4raw-id: //depot/perl@16084
Diffstat (limited to 'pod/perlhack.pod')
-rw-r--r--pod/perlhack.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 986d473ce0..74d8354fbd 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -1683,7 +1683,7 @@ warnings during the compilation phase. Make sure that you mention
this when you post your patch to P5P; the pumpking needs to know this.
When you write your new code, please be conscious of existing code
-conventions used in the perl source files. See <perlstyle> for
+conventions used in the perl source files. See L<perlstyle> for
details. Although most of the guidelines discussed seem to focus on
Perl code, rather than c, they all apply (except when they don't ;).
See also I<Porting/patching.pod> file in the Perl source distribution