On Thursday 21 May 2009 16.26.48 David Cantrell wrote: > One of my distributions is CPAN-FindDependencies. Most of the magic is > wrapped up in a module, and specifically in the > CPAN::FindDependencies::finddeps function. > > There's also a command-line script bundled with it, called cpandeps. > It's doco basically says "takes the same parameters as the finddeps > function". But obviously it would be better to duplicate the doco there > when generating the manpage. > > The obvious solution is to have both module and script #include the > appropriate chunk of POD. > > So I'm thinking: > > =begin cpp > ... > =end cpp > > has anyone already done this? And if not, am I correct in thinking that > I need to write Pod::cpp, have that as a pre-req, and basically follow > the recipe in the Pod::Simple::Subclassing doco?
As rjbs wrote, this is something to do while building your module. any pre-processor would work. cpp and perlpp come to mind and, why not, any templating application or Text::Template. Cheers, Nadim.
