in reply to When do we change our replies?
We could bitch that we don't do "C for loops"
Or, we could consider ourselves Perl programmers, and acknowledge that "there's more than one way of doing it".
But what if they wanted the iteration number?
It's really bad to answers questions by assuming hidden requirements. Not answering is superior in that case. If a requirement isn't in the question, don't assume it is.
each for arrays
On p5p, the current feeling about that is "we wish we never implemented this".
Do we have a common guide to follow when responding to questions here on PM?
A common guide? Buhahahah. It's hard to get consensus even if you were to pick no more than two people from here at random. Other than guides people may have for themselves, there's no guide. Let alone a common one.
This question goes much deeper than coding questions
Actually, I find your questions shallow. Particular the question whether there's a guide: to me it says you're afraid of being yourself, and prefer to follow what someone else cooked up for you. Instead of meekly asking how you should behave, why not tell us how you answer, motivate it, and be prepared for criticism? That maybe useful, as it can help others decide (or change) how to respond.