Occasionally, a question pops up like this one. Basically, the user posts a question about code that works. It seems that this question should be closed, but it's difficult to pick a reasoning to close it. Perhaps adding a statement like "this question answers itself" in the "not a question" category would be helpful? (Or am I out in right field on this one, and the question really shouldn't be closed after all?)
What is meta?
- Any Stack Exchange user can ask a question
- The community provides support, votes on ideas, and reports bugs
- Your voice helps shape the way Stack Exchange operates
It might work for you (and everybody else :p) but is obviously not working for the OP (or not working as expected, etc), or they wouldn't be asking a question.
You are not helping the OP by voting to close. A comment that it works for you and a request for some clarification on the issue the OP is seeing seems to be the way to go to me. If you don't get any reply, THEN vote to close. But voting to close without attempting to help the OP at all seems a bit draconian (and rude).
I've seen many people post working code and their question boils down to "why does this work?". I think these kind of questions are the best. The poster is obviously trying to learn and should be encouraged to do so.
It's a lot like that "give a man a fish and you've fed him for a day, teach him to fish and you've fed him for a lifetime". You throw some code at them and they can deal with that particular situation, you teach them why and how and they can then apply it to other, different situations.