If you've installed Perl, you probably already have perldoc. When you say you couldn't get any help, I'm not sure what you mean. Could you please post the error message?
| [reply] |
If "which perldoc" doesn't come back with the location, do a "find / -name perldoc -print" which will provide the location of the file. If it doesn't find it, verify that you have perl installed (it is installed by default) with "rpm -q perl".
Jason L. Froebe
Team Sybase member No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1
| [reply] |
In the FC3 distribution, perl, perldoc, and the man pages are all part of the same rpm, so you are likely to have them all or nothing.
Can you give a conrete example of running perldoc, showing what you're looking up and the error message you get in return?
Dave. | [reply] |
What exactly is happening? I'm not sure how familiar you are with perldoc, or even what OS you're using.
It took me a while to figure out how to use perldoc on Windows. It isn't a search tool, you have to know what doc you want to read. For example, "perldoc File::Spec" returns the doc for the File::Spec module, but "perldoc while" doesn't find anything, because while doesn't have it's own pod.
In many cases searching perlfunc will return you're looking for. For example, perldoc -f chomp gives you help on the chomp function. Use perldoc perldoc for information on perldoc options.
It's probably best if you browse the online versions of the docs and become familiar with the way things are organized. I use Active State's version extensively. There are others out there, like the documentation on perl.com.
Ardemus
"This, right now, is our lives."
| [reply] |