On Sun, 27 Mar 2005 18:19:22 +0300, Octavian Rasnita wrote:
Have you noticed that "-l" parameter? If it is used, the perldoc command just show the directory where the module is installed.
Teddy
Sigh... did you even try out my example?
He most likely did. Your example works fine here because there is pod in that file at least in some versions.
But you are correct that files without pod will simply generate a "No documentation found..." error. I've never ran into that problem, but then I don't use that "trick" too much prefering the more idiomatic 'perl -MModule -e1'. I saw the perldoc trick mentioned on P5P several years ago, so I usually mention it when this topic comes up as an interesting tidbit.
Randy.
Please read my answer *carefully*, the "perldoc Pod::Perldoc" command will return 'No documentation found for "Pod::Perldoc".' regardless of whether you use the "-l" switch or not, since Pod::Perldoc *has no pod documentation*. However, Pod::Perldoc *is* an installed module. So using "perldoc -l Module::Name" as a means to finding out whether or not a module is installed is not a very robust way of doing it. The other ways posted by various people are much better.
Cheers,
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
