The real complication is parsing the corresponding Perl sub names.
like
- are all sub's source supposed to follow directly to the POD?
- are subs described in head2-items following a special head1-item? (like INTERFACE)
Could you please give us more informations about what you are trying to achieve?
Unfortunately solutions in Perl are not very DRY (thats why I envy Python for stealing docstrings from Lisp)
For instance one of my last employers used a POD server which automatically parsed all installed modules to create CPAN like web-pages including TOCs listing each function/method.
Following the links you got the POD for each sub and the code was JS-folded in between.
Thats what you want? For instance this solution would imply switching from head1 to head2 in your POD.
Cheers Rolf
( addicted to the Perl Programming Language)
In reply to Re: Parse POD of a method from perl module
by LanX
in thread Parse POD of a method from perl module
by perlUser9
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |