> So please, let the parser tell me not only the line of the error, but also the colum.
> Other information currently missing from the message - e.g. column > number, hints about unclosed blocks - is likely to be far more useful >> a) Character count (at line 456, character 23) > >> > >> b) Quote either the remainder or the parsed section on the line (MySQL > >> quotes the remainder, for example) > >> > >> c) Quote the whole line with an indicator where the error occurred. I'm > >> not sure what the best way to do this would be - generically this could > >> be encapsulated in several values: The line content, token start > >> character count, token length / end character count > >> > > > > I really like the combination of A + C. After using php for 13 years the > > If we could do the same as, for example, clang does: just display some > indication where the problem happened within the code, with the line > that caused it. Certainly not displaying internal token names, unless I > am debugging the parser they are useless. > Could this be discussed rather in the "Improvement to errors" thread? https://externals.io/message/110276
