Return to Question

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?

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?

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 perfect 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?

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?

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

When a function call is made by a program, how the called function know how to return to its caller?

It has perfect 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?

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 perfect 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?