Post History

None of these are applicable at least not for Code Golf challenges. I think this community should "opt out" of reactions unless we can come up with more relevant ones.

- "Works for me". Answers are supposed to live up to the challenge specification - if they don't, then one should use comments to point out the problems and possibly down vote if the poster is not responsive. There is no "correct" answer, but a best answer, per language. The score board sorts that out.

- Outdated. Using outdated language features is a common trick and not necessarily considered bad practice for code golf purposes. If the code doesn't work with modern tools/interpreters, then the answer should point out which version it is using. In which case posting an answer for an older version of a language spec is fine.

- Dangerous. The vast majority of the code posted here is blatantly dangerous. Anyone who doesn't grasp that this is a puzzle site but comes here looking for production-quality code only have themselves to blame.