Skip to main content
Post Closed as "Duplicate" by gnat, random
edited tags
Link
gnat
  • 11.3k
  • 26
  • 149
  • 330
edited title
Source Link
user102937
user102937

Flagging When should you decide whether to flag a posted answer as 'NotNot an answer'answer?

When should you decide whether to flag a posted answer as Not an answer?

I've run into this situation a couple of times, where people give an "answer" that basically repeats the problem in the original question. (Not going to give examples here obviously, but it's happened.) So a hypothetical example might be a question like:

I've noticed that addition overflows just get wrapped around in x86. Why?

and a hypothetical non-answer might be something like:

x86 naturally wraps around addition overflows in numbers, just like MIPS and other architectures. You need to be careful when performing arithmetic; check the carry/overflow flags to see if something overflowed.

On the one hand, this doesn't answer the question. But on the other hand, it's well-written (no specific quality issues), and it seems to answer the question.

Should an answer like this be flagged? (Sometimes commenting doesn't help, since there's just no response.)

Flagging as 'Not an answer'

When should you decide whether to flag a posted answer as Not an answer?

I've run into this situation a couple of times, where people give an "answer" that basically repeats the problem in the original question. (Not going to give examples here obviously, but it's happened.) So a hypothetical example might be a question like:

I've noticed that addition overflows just get wrapped around in x86. Why?

and a hypothetical non-answer might be something like:

x86 naturally wraps around addition overflows in numbers, just like MIPS and other architectures. You need to be careful when performing arithmetic; check the carry/overflow flags to see if something overflowed.

On the one hand, this doesn't answer the question. But on the other hand, it's well-written (no specific quality issues), and it seems to answer the question.

Should an answer like this be flagged? (Sometimes commenting doesn't help, since there's just no response.)

When should you decide whether to flag a posted answer as Not an answer?

I've run into this situation a couple of times, where people give an "answer" that basically repeats the problem in the original question. (Not going to give examples here obviously, but it's happened.) So a hypothetical example might be a question like:

I've noticed that addition overflows just get wrapped around in x86. Why?

and a hypothetical non-answer might be something like:

x86 naturally wraps around addition overflows in numbers, just like MIPS and other architectures. You need to be careful when performing arithmetic; check the carry/overflow flags to see if something overflowed.

On the one hand, this doesn't answer the question. But on the other hand, it's well-written (no specific quality issues), and it seems to answer the question.

Should an answer like this be flagged? (Sometimes commenting doesn't help, since there's just no response.)

Source Link
user541686
  • 14.7k
  • 1
  • 26
  • 40

Flagging as 'Not an answer'

When should you decide whether to flag a posted answer as Not an answer?

I've run into this situation a couple of times, where people give an "answer" that basically repeats the problem in the original question. (Not going to give examples here obviously, but it's happened.) So a hypothetical example might be a question like:

I've noticed that addition overflows just get wrapped around in x86. Why?

and a hypothetical non-answer might be something like:

x86 naturally wraps around addition overflows in numbers, just like MIPS and other architectures. You need to be careful when performing arithmetic; check the carry/overflow flags to see if something overflowed.

On the one hand, this doesn't answer the question. But on the other hand, it's well-written (no specific quality issues), and it seems to answer the question.

Should an answer like this be flagged? (Sometimes commenting doesn't help, since there's just no response.)