Why are people closing (er... fine, fine... "putting on hold") questions like this one?

How do called functions return to their caller, after being called?

It has decent spelling and grammar, it's well-tagged, it's understandable, it's quite insightful (it shows the OP is actually thinking about what's happening), and it's 100% programming-related.
(In fact, I can't think of a more programming-related question.)

Why are people closing questions like this one? Could we stop closing everything just because we can?

  • 1
    Voted reopen. The question looks fine to me.
    – Mysticial
    Jul 8, 2013 at 4:18
  • I voted to reopen as well. This sort of question is what we should be encouraging, not shunning.
    – Makoto
    Jul 8, 2013 at 4:20
  • 5
    I don't think the grammar was perfect, but I agree with you about everything else. Jul 8, 2013 at 4:27
  • Delete all the comments! Just a note: I left the one that I felt explained why it isn't off-topic the best, and also left the helpful non-off-topicness-related comment that got buried under all the off-topicness business.
    – animuson StaffMod
    Jul 8, 2013 at 4:35
  • 1
    Yes, we can. (Couldnt stop myself)
    – asheeshr
    Jul 8, 2013 at 4:37
  • Thanks all, that's much better. :)
    – user541686
    Jul 8, 2013 at 4:38

1 Answer 1


It's been reopened now. After a little bit of editing by Lance Roberts and myself, it's a perfectly fine question.

However, I think this is a very rare case. How many times have you seen a good question like this get closed uhh.. on holded? I've only seen two or three.

There are two possible explanations.

  1. Grammar. It's a great question, but it was hiding behind a veil of grammar errors. It took a little bit of cleaning up for me to tell what was being asked. Not a huge deal, but it does lower the question that much more in the sight of the reviewers.

  2. Close-vote piling. Used to indicate the circumstance where new 3k users see the close (1) button and think, 'Hey! Someone else thought that needed closing! I'll help' In this way, a good question can be closed with really only one misplaced vote. Not likely here because all the closers involved had over 10k rep. Scary... but stuff does happen.

  • 5
    I propose a solution: don't show the number of close-votes until the user actually clicks Close, or something like that. (They don't have to vote to see it, but they don't have to see it without asking to, either.) Would that prevent these cases? Maybe I should put a feature request...
    – user541686
    Jul 8, 2013 at 4:39
  • 1
    Oh, and as for how many questions like this I've seen, there have been a few recently, but I'm having trouble finding them. The general trend is that people seem to love closing questions, and it seems like the "on hold" business didn't actually fix it.
    – user541686
    Jul 8, 2013 at 4:42
  • Just added a feature request: meta.stackexchange.com/questions/187800
    – user541686
    Jul 8, 2013 at 6:35
  • I prefer the term "crushed" for "on holdified." It makes the accomplishment sound significant.
    – user206222
    Jul 8, 2013 at 6:53
  • 1
    The close vote queue also had something to do with this. There have been a number of good questions closed as a result of the queue, because it's far easier for people to remove things from that by voting to close than voting to leave them open. Jul 8, 2013 at 14:48

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .