I have a module file that includes packages for helper classes. In outline the file looks something like:
use strict; use warnings; package Segment; sub new { ...; } sub Describe { ...; } package ELF::File; sub new { ...; } sub Describe { ...; } =pod =head1 NAME ELF::File =head1 VERSION ... =head1 USAGE =item C<new(%params)> C<new(...)> creates a new ELF::File object and parses the Program Head +er table and the Section Header table. =item C<Describe()> C<Describe()> returns a multi-line string describing the ELF file head +er contents. ... =cut
Pod::Coverage is happy enough with the ELF::File package, but doesn't see the Segment package. Is there a way to convince Pod::Coverage to notice extra packages in a module and process them? I could move the helpers out into other module files, but that gets pretty silly for some of the helper classes. ELF::File returns helper class objects for some purposes so it is important that their public methods are documented.
In reply to Pod::Coverage for helper classes by GrandFather
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |