First, I must explain something:
Comments are temporary "Post-It" notes left on a question or answer.
You should submit a comment if you want to:
- Request clarification from the author;
- Leave constructive criticism that guides the author in improving the post;
- Add relevant but minor or transient information to a post (e.g. a link to a related question, or an alert to the author that the question has been updated).
Please don't ask that something be converted to a comment when it doesn't resemble the description above. In particular, don't ask that very short or incomplete answers be converted to comments: converting a bad answer into a bad comment just makes everything worse.
Now, on to your flagged posts:
rdtsc accuracy across CPU cores
This isn't link-only. It may not be a good answer, indeed it may be completely wrong - but that's a reason to down-vote, not to flag. Asking moderators to judge the worth of individual answers isn't something you should be doing - you have the tools to do that yourself.
Good 2D Collision Response References
The question asks for books or articles. The answer provides a link to a book. Again, if you don't think it's a good answer then down-vote it; if you think the question is inappropriate, then vote to close it.
Is there a way for continous JSLint validation in Notepad++ or any other IDE?
The question asks for a way to integrate JSLint into an IDE. The answer provides it.
Is there a way for continous JSLint validation in Notepad++ or any other IDE?
See comment for #3.
This is the problem with flagging things based on simple metrics without regard for context.
helpful
instead ofdeclined
. If it's moderated asdeclined
then moderator should leave a proper reason instead of this common comment!declined - No, it's also a crappy comment.