Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

16
  • 2
    This isn't enough data to be an answer, but one could write a analyser with parsekit_compile_string, and put more friendly answers on it. If integrated into your IDE, this could be quite informative. Commented Aug 12, 2013 at 21:49
  • 7
    You put an impressive amount of work into this. Respect for that. It's probably very good for teachers to learn to fast point out errors or for those creating IDEs or implementing quick fixes. However, IDEs will already effectively do most of this work for you, as @Panique suggests. Additionally, im many cases the start again from scratch is a good option.
    – allprog
    Commented Aug 15, 2013 at 12:34
  • 1
    When I Google for the error names listed in the question here, I don't find this post on even the first page of Google, ever. That's a huge waste of what is otherwise fantastic work! Googling "unexpected T_STRING" gets me this piece of garbage which has 50% as many views as your entire error reference here. This could be solved easily by extracting out Q&A pairs with good titles. See also: meta.stackoverflow.com/questions/314618/…
    – Mark Amery
    Commented Jan 23, 2016 at 16:17
  • 2
    @Fred-ii- I think most causes are similar to the T_IF / T_FOREACH / ... block. Albeit I wanted to compile a more custom summary for IF/ELSE/ELSEIF questions.
    – mario
    Commented May 28, 2016 at 13:45
  • 2
    @β.εηοιτ.βε Great idea; there've been quite a handful of these questions recently. Though it would need to cover the three common cases (import scope, traits, closures) if possible.
    – mario
    Commented Aug 22, 2019 at 14:16