Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

I was the one who deleted your answer herehere in response to a "not an answer" flag. I often leave the following comment to answers like this:

If you have a new question to ask, please do so as such. If you need to, you can refer to this question in your own. Because this was placed in an answer, no one will be able to respond to you and I'm going to need to remove this to keep things clean.

but forgot to in this case.

Stack Overflow is intentionally structured differently than the forums that most people are used to. The concept of one question followed only by answers is intended to address the common problem of having to dig through pages of responses to find valuable information in a forum thread. As such, follow-on questions don't work well at all when left as answers to questions on Stack Overflow.

In addition to the philosophical opposition to follow-on questions, there are technical issues in how people can respond to you when you ask a question in an answer. They only can comment on your "answer", and the normal voting system doesn't apply. This quickly turns into a mess, as we found out in many non-answers like this.

What you're asking in your follow-on could make for a good standalone question by itself. You could quote the code they used in your new question, referring back to their original question and answer, and explain some of the problems you're having in your case.

I see you left a comment about this, but a comment is only going to be visible to the answerer and anyone who stops by. A new standalone question could get good, fast answers from a variety of people. Also, they'd be able to provide code in their answers, which could be difficult to format right in a reply to your comment.

I was the one who deleted your answer here in response to a "not an answer" flag. I often leave the following comment to answers like this:

If you have a new question to ask, please do so as such. If you need to, you can refer to this question in your own. Because this was placed in an answer, no one will be able to respond to you and I'm going to need to remove this to keep things clean.

but forgot to in this case.

Stack Overflow is intentionally structured differently than the forums that most people are used to. The concept of one question followed only by answers is intended to address the common problem of having to dig through pages of responses to find valuable information in a forum thread. As such, follow-on questions don't work well at all when left as answers to questions on Stack Overflow.

In addition to the philosophical opposition to follow-on questions, there are technical issues in how people can respond to you when you ask a question in an answer. They only can comment on your "answer", and the normal voting system doesn't apply. This quickly turns into a mess, as we found out in many non-answers like this.

What you're asking in your follow-on could make for a good standalone question by itself. You could quote the code they used in your new question, referring back to their original question and answer, and explain some of the problems you're having in your case.

I see you left a comment about this, but a comment is only going to be visible to the answerer and anyone who stops by. A new standalone question could get good, fast answers from a variety of people. Also, they'd be able to provide code in their answers, which could be difficult to format right in a reply to your comment.

I was the one who deleted your answer here in response to a "not an answer" flag. I often leave the following comment to answers like this:

If you have a new question to ask, please do so as such. If you need to, you can refer to this question in your own. Because this was placed in an answer, no one will be able to respond to you and I'm going to need to remove this to keep things clean.

but forgot to in this case.

Stack Overflow is intentionally structured differently than the forums that most people are used to. The concept of one question followed only by answers is intended to address the common problem of having to dig through pages of responses to find valuable information in a forum thread. As such, follow-on questions don't work well at all when left as answers to questions on Stack Overflow.

In addition to the philosophical opposition to follow-on questions, there are technical issues in how people can respond to you when you ask a question in an answer. They only can comment on your "answer", and the normal voting system doesn't apply. This quickly turns into a mess, as we found out in many non-answers like this.

What you're asking in your follow-on could make for a good standalone question by itself. You could quote the code they used in your new question, referring back to their original question and answer, and explain some of the problems you're having in your case.

I see you left a comment about this, but a comment is only going to be visible to the answerer and anyone who stops by. A new standalone question could get good, fast answers from a variety of people. Also, they'd be able to provide code in their answers, which could be difficult to format right in a reply to your comment.

Source Link
Brad Larson Mod
  • 60.9k
  • 23
  • 124
  • 230

I was the one who deleted your answer here in response to a "not an answer" flag. I often leave the following comment to answers like this:

If you have a new question to ask, please do so as such. If you need to, you can refer to this question in your own. Because this was placed in an answer, no one will be able to respond to you and I'm going to need to remove this to keep things clean.

but forgot to in this case.

Stack Overflow is intentionally structured differently than the forums that most people are used to. The concept of one question followed only by answers is intended to address the common problem of having to dig through pages of responses to find valuable information in a forum thread. As such, follow-on questions don't work well at all when left as answers to questions on Stack Overflow.

In addition to the philosophical opposition to follow-on questions, there are technical issues in how people can respond to you when you ask a question in an answer. They only can comment on your "answer", and the normal voting system doesn't apply. This quickly turns into a mess, as we found out in many non-answers like this.

What you're asking in your follow-on could make for a good standalone question by itself. You could quote the code they used in your new question, referring back to their original question and answer, and explain some of the problems you're having in your case.

I see you left a comment about this, but a comment is only going to be visible to the answerer and anyone who stops by. A new standalone question could get good, fast answers from a variety of people. Also, they'd be able to provide code in their answers, which could be difficult to format right in a reply to your comment.