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

In this question, http://codereview.stackexchange.com/q/107700/78136https://codereview.stackexchange.com/q/107700/78136, the OP has not gotten the code to compile, and is on its way to be closed. This I understand, and are not debating.

My question, however, is whether it is according to site policy to give comments like the one I've given suggesting a missing brace. Or possibly comment other stuff which would make the code working, albeit possibly flawed, which in turn would render the question to be a legal question on Code Review. (And thus legible for reopening, if already closed)

Added: The icky part, for me, is that the correction does possibly encourage editing of code which is not something we want in general for a question.

In this question, http://codereview.stackexchange.com/q/107700/78136, the OP has not gotten the code to compile, and is on its way to be closed. This I understand, and are not debating.

My question, however, is whether it is according to site policy to give comments like the one I've given suggesting a missing brace. Or possibly comment other stuff which would make the code working, albeit possibly flawed, which in turn would render the question to be a legal question on Code Review. (And thus legible for reopening, if already closed)

Added: The icky part, for me, is that the correction does possibly encourage editing of code which is not something we want in general for a question.

In this question, https://codereview.stackexchange.com/q/107700/78136, the OP has not gotten the code to compile, and is on its way to be closed. This I understand, and are not debating.

My question, however, is whether it is according to site policy to give comments like the one I've given suggesting a missing brace. Or possibly comment other stuff which would make the code working, albeit possibly flawed, which in turn would render the question to be a legal question on Code Review. (And thus legible for reopening, if already closed)

Added: The icky part, for me, is that the correction does possibly encourage editing of code which is not something we want in general for a question.

added 158 characters in body
Source Link
holroy
  • 11.8k
  • 10
  • 15

In this question, http://codereview.stackexchange.com/q/107700/78136, the OP has not gotten the code to compile, and is on its way to be closed. This I understand, and are not debating.

My question, however, is whether it is according to site policy to give comments like the one I've given suggesting a missing brace. Or possibly comment other stuff which would make the code working, albeit possibly flawed, which in turn would render the question to be a legal question on Code Review. (And thus legible for reopening, if already closed)

Added: The icky part, for me, is that the correction does possibly encourage editing of code which is not something we want in general for a question.

In this question, http://codereview.stackexchange.com/q/107700/78136, the OP has not gotten the code to compile, and is on its way to be closed. This I understand, and are not debating.

My question, however, is whether it is according to site policy to give comments like the one I've given suggesting a missing brace. Or possibly comment other stuff which would make the code working, albeit possibly flawed, which in turn would render the question to be a legal question on Code Review. (And thus legible for reopening, if already closed)

In this question, http://codereview.stackexchange.com/q/107700/78136, the OP has not gotten the code to compile, and is on its way to be closed. This I understand, and are not debating.

My question, however, is whether it is according to site policy to give comments like the one I've given suggesting a missing brace. Or possibly comment other stuff which would make the code working, albeit possibly flawed, which in turn would render the question to be a legal question on Code Review. (And thus legible for reopening, if already closed)

Added: The icky part, for me, is that the correction does possibly encourage editing of code which is not something we want in general for a question.

Source Link
holroy
  • 11.8k
  • 10
  • 15

Commenting on faulty code

In this question, http://codereview.stackexchange.com/q/107700/78136, the OP has not gotten the code to compile, and is on its way to be closed. This I understand, and are not debating.

My question, however, is whether it is according to site policy to give comments like the one I've given suggesting a missing brace. Or possibly comment other stuff which would make the code working, albeit possibly flawed, which in turn would render the question to be a legal question on Code Review. (And thus legible for reopening, if already closed)