These questions (on the whole) are welcome, so long as they meet several criteria (and these are criteria that apply to every question, but bear repeating):
- They must have a good title that explains the issue (hint: "What is wrong with my code?" is not a good title)
- They should contain an SSCCE (Part of the SSCCE is "Short". A code dump that scrolls is not short)
- They should include the error message. This is what future users will search for when they have a problem.
- The user should explain what they've tried, what hasn't worked, and what they expect to happen.
If these criteria are followed, then there's a good likelihood that future users will benefit both from the question and its answers.
Keep in mind, this is not for every syntax error or typo question out there. There are still instances where no matter how the user phrases the question, it won't be helpful to others. I address this below.
Users search on error messages, and any answers that explain the error message in depth and how to fix it are good answers. We can't have good answers if we don't allow people to ask questions because their error message indicates a syntax or logic error.
There are several ways these types of questions can be closed, depending on what's wrong with them:
No good title or just a long code dump with a "What's wrong with my code?": -> off topic
Questions concerning problems with code you've written must describe the specific problem and include valid code to reproduce it. See SSCCE.org for guidance.
Short code dump, but the user forgot how to spell their own name?. I argue they didn't have a minimal understanding of the problem: -> off topic
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Tell us what you've tried to do, why it didn't work, and how it should work. See also: Stack Overflow question checklist
Can't figure out what they're even asking for? ->unclear what you're asking:
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking.
The reason 'Too Localized' was taken away was because it was being used on questions it should not have been used on way too often. Questions with syntax errors are a part of programming. It is inappropriate for us to close questions that meet the criteria I listed for a good question, even if it's because the OP made a stupid mistake.
The good news is that most 'typo' questions that meet my criteria have been asked before, if they have a good answer, feel free to mark them as duplicates. Of course, the whole duplicate question thing is a whole 'nother issue.
Keep in mind, we want Stack Overflow to be a repository of useful programming knowledge. That means that users shouldn't have to go to forums to find out what error messages mean.