There's a difference between knowing the path and walking the path.
I can only show you the door. You must walk through it.
I don't think it is too much to show effort before posing a question. An excellent method is to post a code sample, even a bad one, and show the output. Otherwise, the responder may not wish to expend more time answering the question than the poster took trying to find the solution.
Indeed, the methodology used to find the solution to one problem tends to evolve over time and experience, becoming multifacited and applicable outside of perl. It just helps finding answers down the road (not to mention helps asking the right question).
crazyinsomniac's point, IMHO YMMV, is that let us not address the symptom (the cgi sample question in the discussion root node, for example). Let's address the source cause (learn the language and how it works via books, trial and error, classes, etc. before throwing one's hands up.).
HTH
--
idnopheq
Apply yourself to new problems without preparation, develop confidence in your ability to to meet situations as they arrise.
In reply to Re: (crazyinsomniac) Re: Don't just provide a module name
by idnopheq
in thread Don't just provide a module name
by gryphon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |