If you don't do your homework, you don't get to Perl
One of the most common responses to simple, text-book-quality questions on many Perl community outlets is "We are not here to do your homework". It's usually thrown in a swift, abase, manner, as if saying "How DARE you ask us to answer your assignment for you?!", and at times is accompanied by a general comment as to the asker's intelligence, seriousness, effort, capabilities, values, ethics and sexual capabilities. It is also, always, the most incorrect response possible.
One of my first assignment, back when I was a technical supporter, was to "refactor" a Perl script, which turned out to be more of a glorified shell script riddled with back-ticked system calls to wget, grep, et al. After rewriting those as actual Perl, I was left with the last element of the script that I wanted, upper-casing text in the files the script downloaded. The problem wasn't of how to perform the upper-casing, but how to perform it under specific terms, but before I got to that, I thought the best way would be to grab the text I needed using a regexp, then maybe substituting it using s///, now, what is the best way to uppercase text with a regexp?
I can only imaging what would've happened had I attempted to post that question to a PerlMonks thread, or an IRC channel. While it does look like a sort of Perl beginner course assignment, It wasn't. Perl is like that. The amount of things to know before you can hack some baby-Perl script is amazingly minimal, and Perl's DWIM design doesn't enforce you to understand why do things work the way they do, so the learning curve is shallow, and no-one can really say whether a question is from a course, or a real-world I-need-this-for-my-job question.
And even if it is homework, what of it? Why not just help the guy out, and allow him to progress faster to the more interesting parts of Perl?