The documentation for Module.pm is written into Module.pod and calling perldoc Module shows the generated content in Module.pod (see perldoc )³.

To keep it synchronized I've integrated the call to my podbuilder.pl script into my test suite as “pseudo test“.

Since I never release² without testing¹, my documentation is always up to date and if podbuilder.pl fails then my test suite fails too.

(actually I still have to teach git-commit to stop telling that Module.pod has changed, don't wanna be told anymore about the obvious ;)

Works for me! :)

HTH!

¹) Using the modulino principle to run the test suite facilitate things a lot.

²) even hardly ever commit w/o testing...

³) perldoc Module.pm for my internal developer documentation