There's more than one way to do things | |
PerlMonks |
POD, come let me see thee, I have thee not, but still I clutch theeby Bloodnok (Vicar) |
on Dec 18, 2008 at 15:07 UTC ( [id://731273]=perlquestion: print w/replies, xml ) | Need Help?? |
Bloodnok has asked for the wisdom of the Perl Monks concerning the following question:
Felicitations of the season to all you venerable monks out there ,
Having had a bit of a Super Search round (initially, I tried googling myself silly ... but enjoyed it far too much), I don't seem to be able to find what I'm looking for .. but then again it could be that I'm not asking quite the right question ;-) This time, the question to which I seek an answer is (takes deep breath and asks more in hope than expectation) ... Does anybody know of a way to use perldoc (or an alternative) in a manner similar to the perldoc -f <func> command to list the doc for a built-in. The difference being that I'd like to run it against any CPAN/bespoke module such that the given functions' doc is listed from said module e.g. perldoc -f sub Foo::Bar to list the doc for Foo::Bar::sub() ... c/w perldoc Foo::Bar and get the user to trawl thro' looking for the requisite information on sub. TIA , Sits back to await xmas and enlightening answers - but not necessarily in that order :-) Update: .oO(Hmmm, maybe emulate perldoc itself - getting the wanted behaviour by overloading one/some of the Pod::Perldoc::* methods as appropriate i.e. iff called with -f & 2 args and then handing off to perldoc itself...)
A user level that continues to overstate my experience :-))
Back to
Seekers of Perl Wisdom
|
|