The 'perldoc' command, despite sometimes being split out from the distribution of Perl in some OS packages and/or core OS installs, is important to have installed. It provides access to documentation about the core language as well as to the included libraries (modules). While it's entirely possible to program Perl on a system that doesn't have perldoc installed, it's pretty darn near impossible for someone to program effectively and efficiently without some type of access to perldoc's functionality. (and hence to easily accessible and readable documentation in general) In short, having access to the proper documentation for your language should fall under 'having the appropriate tools to work effectively' and is the responsibility of your employer to provide. At the risk of making an assumption about your current situation, I can't help but find it somewhat sadistic that your employer both does not provide the documentation for a language they've assigned a task for and also will not provide the required tools to do your work when requested with the vague reasoning of 'not enough disk space'. Surely you can approach your employers and request that you either be permitted to have access to the documentation for the version of Perl you're working with, possibly on your workstation itself, or possibly via access to a website that has them. You should pay keen attention to finding the documentation appropriate for the version of Perl that you are working with as the language has changed quite significantly in its lifetime. In addition, although the pointers to documentation that you've received were in response to your original request for information related to 'goto', however I would expect that you'll be very likely to require additional information that is clearly illustrated in the documentation in the future. I hope that you are able to acquire what you need. Good luck!
| [reply] |
Whoa there, big fella! No point in falling to the level of whoever is baiting you. :)
I see you've been around the Monastery for a while, albeit intermittently, so you ought to know how things are done around here. At the risk of giving unwanted advice, I have three comments:
- If someone posts something that you think is intended to offend, try responding positively or neutrally. This avoids misunderstanding (in case the offense was unintentional) and shows you to be a level-headed guy who others will want to help. I can't think that insults are ever warranted even toward anonymous monks -- they just make you look juvenile.
- If you're asking for help, try to remember that others are taking time from their busy schedules to assist you, and that they don't owe you anything (unless you have previously helped them). Humility should be your watchword -- keep your arrogance for when you answer other people's posts (or better yet, keep it suppressed altogether).
- Unix is an operating system, not a language, as far as I know. I have encountered many shell scripts, particularly Korn shell scripts, but (at least for those more familiar with Unix) the phrase "written in UNIX" seems nonsensical. Admittedly, many folks probably understand what you meant, but the lack of specificity makes one wonder about your knowledge of whatever shell the script is written in.
In spite of what may seem a patronizing tone, my comments here are kindly meant, and may help you to make PerlMonks a more positive place for all of us. I'm not the anonymous monk(s) with whom you have been sparring, just in case you wondered. Try to view this interchange with a sense of humor, and take yourself a little less seriously. :)
No good deed goes unpunished. -- (attributed to) Oscar Wilde
| [reply] |
I didn't think this could get any better, but it does. So not only does your employer stupidly restrict web access, they also refuse to give you access to the proper documentation for the programming language you use? Tell me, do they also tie one of your arms behind your back? Do they blindfold you when you get into work in the morning? Or maybe they just go with a frontal lobotomy after you sign the employment contract (that would certainly explain some of the posts in this thread).
How is this your fault? Easy, if you weren't such a loser you wouldn't be desparate enough to work at the shitty job you apparently have.
And since you still don't seem to get it, saying that a system is "written in UNIX" is as nonsensical as saying something is "written in Windows". UNIX is an operating system, not a scripting language, and what you're talking about are shell scripts. Anyone who has allegedly been in computing for over thirty years and doesn't know that must have been going through life with both eyes shut and the brain addled by interesting chemicals. Which again makes perfect sense, given the quality of your posts. (See, you can't just go and throw in insults without context, you gotta lead up to them or else you lose the non-toking segment of your audience.) | [reply] |
