|Perl: the Markov chain saw|
Re: When do we change our replies?by ww (Bishop)
|on Apr 16, 2012 at 02:01 UTC||Need Help??|
"We could bitch that we don't .... "
Or, we could point out that using a C-style loop is un-lazy and thus unPerlish, without bitching. Without the explanation of why we offer the alternate syntax, the reply probably wouldn't be much help to a newcomer... and a newcomer who takes the trouble to include code, pay attention to formatting and some of the other desiderata listed in our FAQs deserves (IMO) the best possible answer... given any shortcomings (if any) in the problem statement.
"But what if they wanted the iteration number? "
Again, IMO, if they didn't mention that in the OP or a follow up, should we try to use our broken crystal balls to guide our replies?
As to a common guide, which I believe is the subject of your question given the amplification in your last sentence, "Is there consistency is my inquiry..." -- I'm not aware of one, other than the examples provided by the most knowledgeable and helpful Monks. And as several recent threads have highlighted, there's certainly something less than consensus about just how to handle the worst of poorly written questions and the "gimme's."Addendum:
Suppose the next SOPW you see goes like this:
Is A1 a "good" answer: I would argue 'yes' as it tells someone who looks to be a beginner how to find some documentation... a skill that beginner will need to progress beyond the novice level.
But how about answer A2a thru A2c: To my taste, c is the best answer, because the writer now has some evidence that the OP is looking for a script rather than information or knowledge... a view that (in my eyes) is reinforced by the OP's final statement.
That said, if you emulate the form of replies you admire, you'll develop your own style of helpful responses.