php-src/Zend/tests/bug60099.phpt

--TEST--
Bug #60099 (__halt_compiler() works in braced namespaces)
--FILE--
<?php
namespace foo {
    __halt_compiler();

?>
--EXPECTF--
Parse error: Unclosed '{' on line 2 in %s on line %d
- Fixed bug #60099 (__halt_compiler() works in braced namespaces) 2011-11-16 17:41:40 +00:00			`--TEST--`
			`Bug #60099 (__halt_compiler() works in braced namespaces)`
			`--FILE--`
			`<?php`
			`namespace foo {`
Reindent phpt files 2020-02-03 21:52:20 +00:00			`__halt_compiler();`
- Fixed bug #60099 (__halt_compiler() works in braced namespaces) 2011-11-16 17:41:40 +00:00
			`?>`
			`--EXPECTF--`
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-08 11:19:39 +00:00			`Parse error: Unclosed '{' on line 2 in %s on line %d`