This question already has an answer here:
This question is an attempt to clear up the following part of a related question:
Do not use this flag when a user posts:
- An answer to a (slightly) different question
in the case of an answer to an entirely different question. It boils down to "Where do we draw the line" because any affirmative sentence is an answer to some question and any affirmative sentence with a programming context is a possible answer to a possible question on StackOverflow.
The background here is the linked answer to https://stackoverflow.com/questions/22185002/what-exactly-do-these-lines-say/22185141#22185141
This answer has nothing to do with the question, but merely gives information the answerer believes could help the asker in a general sense. If you read the question, you see that it's about a specific syntax element in jQuery (it's properly tagged as well).
The answer doesn't address that in any way, but rather gives (possibly helpful) advice in a different direction, maybe referring to the asker's obvious lack of background knowledge as a whole.
While the answer might be helpful, I think it's appropriate to flag it as "Not an answer" because it's an answer to an entirely different question than the one it was posted to. But my flag was declined, so I'm unsure if I understand the concept correctly and would like to understand the thought process behind the decline.
The decline message is
declined - a moderator reviewed your flag, but found no evidence to support it.
A related case where I didn't flag because I wasn't sure it was appropriate (but would flag for the same reason) is this question. The first comment to the question was originally an answer and I commented it to point out it's helpful advice, but not answering the question. Obviously, the author agreed.