There's more than one way to do things | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
perldoc allows you to provide a file path rather than a module name...
I tend to view my pod in an 80x24 terminal to check there's no ugly line wrapping issues at that size. I also check with Test::Pod and Test::Pod::Coverage.
perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'
In reply to Re^3: how do you build and test your modules locally before publishing
by tobyink
|
|