diff options
| author | Philip Newton <pne@cpan.org> | 2001-11-24 22:24:00 +0100 |
|---|---|---|
| committer | Jarkko Hietaniemi <jhi@iki.fi> | 2001-11-24 20:09:20 +0000 |
| commit | 9d077eaaaaf5479060d3eabcfb6d60f086ba857a (patch) | |
| tree | f0d5377c72e9ecc2a380f1bba34eb8a263d88ddd /pod | |
| parent | d6ec9fa3b3319f35131489112ca8c41e368dd1c8 (diff) | |
| download | perl-9d077eaaaaf5479060d3eabcfb6d60f086ba857a.tar.gz | |
Re: [PATCH] Tests are good
Message-ID: <4c000us22s27871hrsqnvjmtnvtd4r85u1@4ax.com>
p4raw-id: //depot/perl@13245
Diffstat (limited to 'pod')
| -rw-r--r-- | pod/perlhack.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod index 371b6b5f72..1f69c969ee 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -164,7 +164,7 @@ must include regression tests to verify that everything works as expected. Without tests provided by the original author, how can anyone else changing perl in the future be sure that they haven't unwittingly broken the behaviour the patch implements? And without tests, how can the patch's author be -confident that his/her hard work put into the patch won't be accidently +confident that his/her hard work put into the patch won't be accidentally thrown away by someone in the future? =item Is there enough documentation? |