diff options
| author | Karl Williamson <public@khwilliamson.com> | 2011-09-22 09:19:02 -0600 |
|---|---|---|
| committer | Karl Williamson <public@khwilliamson.com> | 2011-09-22 09:24:13 -0600 |
| commit | 204c23833e7aa6efc02cbe7e7e42dc93be0d64b1 (patch) | |
| tree | 3de1df447b5aa2b909a13e1536acc434a38988b2 | |
| parent | 44b8cd40028f888cba315a74e0beb8e85c6ec9d1 (diff) | |
| download | perl-204c23833e7aa6efc02cbe7e7e42dc93be0d64b1.tar.gz | |
podcheck.t: clarify its pod
| -rw-r--r-- | t/porting/podcheck.t | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/t/porting/podcheck.t b/t/porting/podcheck.t index 85e44922d7..817814e426 100644 --- a/t/porting/podcheck.t +++ b/t/porting/podcheck.t @@ -115,11 +115,13 @@ A number of issues raised by podcheck.t and by the base Pod::Checker are not really problems, but merely potential problems, that is, false positives. After inspecting them and deciding that they aren't real problems, it is possible to shut up this program -about them, unlike base Pod::Checker. To do this, call podcheck.t with the -C<--regen> option to regenerate the database. This tells it that all existing +about them, unlike base Pod::Checker. For a valid link to an outside module +or man page, call podcheck.t with the C<--add_link> option to add it to the +the database of known links; for other causes, call podcheck.t with the C<--regen> +option to regenerate the entire database. This tells it that all existing issues are to not be mentioned again. -This isn't fool-proof. The database merely keeps track of the number of these +C<--regen> isn't fool-proof. The database merely keeps track of the number of these potential problems of each type for each pod. If a new problem of a given type is introduced into the pod, podcheck.t will spit out all of them. You then have to figure out which is the new one, and should it be changed or not. @@ -137,7 +139,8 @@ the number of those problems for that pod to a negative number. This will cause the corresponding error to always be suppressed no matter how many there actually are. -There is currently no check that modules listed as valid in the data base +Another problem is that there is currently no check that modules listed as +valid in the data base actually are. Thus any errors introduced there will remain there. =head2 Specially handled pods @@ -149,7 +152,7 @@ actually are. Thus any errors introduced there will remain there. This pod is generated by pasting bits from other pods. Errors in those bits will show up as errors here, as well as for those other pods. Therefore errors here are suppressed, and the pod is checked only to verify that nodes -within it that are externally linked to actually exist. +within it actually exist that are externally linked to. =item perldelta |