Your skill will accomplish what the force of many cannot |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Just an email signature. For some gleeful fun, run that with -w ;-P That said, yes, almost all answers to any question about perl have already been given, specially if we're not dealing with obscure edge cases or being hooked upon blead perl. Sometimes advice which empowers the questioner to solve their problem on their own ist best. Then, it is all about economics. Of course not all perl programmers have a deep knowledge about the platform they work upon, and for most cases that's not even necessary, since perl is very good at abstracting away the intrinsics. So, sometimes it is just more efficient to ask, say, on IRC <me> I am having problems installing Foo. I get Can't exec "bar_blurb": No such file or directory instead of prodding e.g. the depths of my OS and its package manager (but imho to be a really good perl programmer, you have to know your platform and its tools). Last, we are all being blind. Of course it is all documented in the manual pages. But which one? If I am able to make a good educated guess, I grep the pod section, but what if I don't? Blindness is even more the case when it comes to bugfixing, because I don't write code to write bugs, and so finding my very own bugs is the most tiresome and tedious work I have to do once in a while, and at the end there's mostly *facepalm*. In contrast, finding a bug in someone elses code often is only a matter of minutes. My knowledge is obvious to me, but not to others, and I can only guess (sometimes) what knowledge they have. But overall, most Monks know the points I addressed, are being very polite and tolerant and going much out of their way to answer things, some casual misinterpretations nonwithstanding.
perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'
In reply to Re: RTFM!!!!! (but if you didn't, no biggie)
by shmem
|
|