If you want to automate some documentation features with regards to inheritance and role composition, you can use these two modules:
https://metacpan.org/module/Pod::Weaver::Section::Extends https://metacpan.org/module/Pod::Weaver::Section::Consumes Mike On Tue, Dec 18, 2012 at 2:52 PM, Maurice Mengel <mauricemen...@gmail.com> wrote: > Thanks for quick replies! Lot's of good stuff. > > Personally, I am not a fan of documenting anything twice, so I don't like > to document inherited stuff in the inheriting class, but I have seen > modules that seem to create documentation automatically. That might work > (in many cases), especially if you are the author of the other class. > > I'd prefer to link to the parent/role class. I suspect that could also be > automatized with podweaver. But before I even think about that I think > someone should propose a standard (or two) for how classes should be > described in pod. As far as I can tell/remember, such a standard is not > covered by any of the perl books, the new perlootut ( > http://perldoc.perl.org/perlootut.html) or the Moose manual. > > Thanks for the code and the weaver.ini. I will study those. Both look > great. I should be able to come up with a solution that works for me based > on this. Thanks again! > > On Tue, Dec 18, 2012 at 12:08 PM, Nick Perez <n...@nickandperla.net> wrote: > >> o has an attempt at "inherited" documentation, but I am not >> too sure h >>
