It's not properly tagged either. Like I said, all the questions I speak of are answerable, and are not typos. They all have a clear, and possibly good answer. They're poorly written and too localized though, and are duplicates, but not exact duplicates
@LaszloPapp yeah, "Issue with printing pointer address" is a good title in retrospect, but I'm not sure OP knows that he is in fact printing a pointer address, what a pointer is, or what a dereference operator is. He might have seen that in a scanf and put it in a printf by mistake.
OP didn't ask what a pointer is, what a pointer address is, or what printing a pointer address does simply because they did not know what those things were when asking the quesiton.
@LaszloPapp perhaps, but it is changing the quesiton, it means we're solving OP's XY problem for them, I'm not sure that's a bad thing, but it's certainly not what people do most of the time and it can also usually only be done in retrospect.
Yeah, but I would feel uneasy closing it since it's not an exact duplicate. I agree with the sentiment but I'm not sure about the course of action. That sort of edit seems too radical, although I agree it's helpful.
Closing it and guiding OP to the canonical resource where they'd find about pointers anyway, while making a stand on asking such questions, although that's probably less useful. It's also a lot of work.
Yeah, I didn't like "Lack of Understanding" either, that's really what that question is all about.
"Lack of Understanding" was bad because it was rude and easily abused, I think we can do better.
stackoverflow.com/questions/23621033/… here is another example, a code request, although this is actually a really clear VBA question had OP phrased it more clearly.
Stuff like this question about not understanding C# context. It can be closed as a dupe of "How does scoping work in C#" if there were such a question I guess though.
this is also too localized, but not a dupe and pretty clear.
Following our chat conversation with Benjamin, I would suggest to extend the "lacks information" close reason with information about what the OP has tried, and not just about "diagnosing the problem", or well, if the current text is supposed to mean that, how about clarifying it?