The problem is that it's a one-shot joke, and therefore pretty much not funny at all after you see it once.
I'd gently suggest that this boilerplate response is more useful:
It looks like the CPAN module X can solve the problem you have (see [c
+pan://X]).
I found this via http://search.cpan.org, by entering "search term".
Here's how you could use it:
And then invest the time in showing how that module would solve the problem, even if it's just an outline of what subs or methods you'd use in doing so. This is a much more useful answer to the question, as it gently prods the original poster in the direction of actually trying your suggestion, and tells them that search.cpan.org is a good first place to go when looking for something.
I don't want to discourage people from responding to posts - but I do want to discourage them from taking cheap shots at the querents, and the implication of the "let me X that for you" sites is "Hey, you're stupid. You didn't search first", as opposed to "let me give you a pointer to something that will help".
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|