php-src/tests
Alex Dowad 80598f1250 Syntax errors caused by unclosed {, [, ( mention specific location
Aside from a few very specific syntax errors for which detailed exceptions are
thrown, generally PHP just emits the default error messages generated by bison on syntax
error. These messages are very uninformative; they just say "Unexpected ... at line ...".

This is most problematic with constructs which can span an arbitrary number of lines, such
as blocks of code delimited by { }, 'if' conditions delimited by ( ), and so on. If a closing
delimiter is missed, the block will run for the entire remainder of the source file (which
could be thousands of lines), and then at the end, a parse error will be thrown with the
dreaded words: "Unexpected end of file".

Therefore, track the positions of opening and closing delimiters and ensure that they match
up correctly. If any mismatch or missing delimiter is detected, immediately throw a parse
error which points the user to the offending line. This is best done in the *lexer* and not
in the parser.

Thanks to Nikita Popov and George Peter Banyard for suggesting improvements.

Fixes bug #79368.
Closes GH-5364.
2020-04-14 11:22:23 +02:00
..
basic Improve undefined variable error messages 2020-03-31 13:02:32 +02:00
classes Improve undefined variable error messages 2020-03-31 13:02:32 +02:00
func Reindent phpt files 2020-02-03 22:52:20 +01:00
lang Syntax errors caused by unclosed {, [, ( mention specific location 2020-04-14 11:22:23 +02:00
output Change argument error message format 2020-02-26 15:00:08 +01:00
run-test Remove track_errors and $php_errormsg 2019-01-28 15:58:23 +01:00
security Reindent phpt files 2020-02-03 22:52:20 +01:00
strings Reindent phpt files 2020-02-03 22:52:20 +01:00
quicktester.inc Reindent phpt files 2020-02-03 22:52:20 +01:00