diff options
| author | Abhijit Menon-Sen <ams@wiw.org> | 2001-11-16 12:11:14 +0000 |
|---|---|---|
| committer | Abhijit Menon-Sen <ams@wiw.org> | 2001-11-16 12:11:14 +0000 |
| commit | 210b36aa2e9e009554be8970c3315c2658c0384f (patch) | |
| tree | 71bb13e291837569d86a3f2f5c17515ccc1b9610 /pod/perlhack.pod | |
| parent | d7ceb7fc1159206a67f149394fc7aa55f6b4f7dd (diff) | |
| download | perl-210b36aa2e9e009554be8970c3315c2658c0384f.tar.gz | |
[PATCH] Doc spellcheck + podcheck
From: Autrijus Tang <autrijus@egb.elixus.org>
Date: Thu, 15 Nov 2001 22:49:05 -0800
Message-Id: <20011116064905.GA44092@egb.elixus.org>
Subject: [PATCH] podcheck+spellcheck, the rest of the story
From: Autrijus Tang <autrijus@egb.elixus.org>
Date: Fri, 16 Nov 2001 00:42:20 -0800
Message-Id: <20011116084220.GA44295@egb.elixus.org>
Subject: Re: [PATCH] podcheck+spellcheck, the rest of the story
From: Nicholas Clark <nick@ccl4.org>
Date: Fri, 16 Nov 2001 10:32:01 +0000
Message-Id: <20011116103200.F62891@plum.flirble.org>
(Applied after suitable de-mangling.)
p4raw-id: //depot/perl@13041
Diffstat (limited to 'pod/perlhack.pod')
| -rw-r--r-- | pod/perlhack.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod index 66a8ea0db6..49d7625ab0 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -1638,7 +1638,7 @@ extremely important to test any addition thoroughly and add new tests to explore all boundary conditions that your new function is expected to handle. If your new function is used only by one module (e.g. toke), then it should probably be named S_your_function (for static); on the -other hand, if you expect it to accessable from other functions in +other hand, if you expect it to accessible from other functions in Perl, you should name it Perl_your_function. See L<perlguts/Internal Functions> for more details. @@ -1679,7 +1679,7 @@ Lastly, TEST TEST TEST TEST TEST any code before posting to p5p. Test on as many platforms as you can find. Test as many perl Configure options as you can (e.g. MULTIPLICITY). If you have profiling or memory tools, see L<EXTERNAL TOOLS FOR DEBUGGING PERL> -below for how to use them to futher test your code. Remember that +below for how to use them to further test your code. Remember that most of the people on P5P are doing this on their own time and don't have the time to debug your code. |