php-src/Zend/tests/ns_088.phpt

--TEST--
Nested group use statements syntax error
--FILE--
<?php
namespace Fiz\Biz\Buz {
    use Foo\Bar\Baz\{
        A,
        B {
            C
            D,
            E
        }
    };
}
?>
--EXPECTF--
Parse error: syntax error, unexpected token "{", expecting "}" in %s on line %d
add tests for batch use declarations with classes, functions and constants 2015-01-19 05:21:11 +00:00			`--TEST--`
fix compilation warnings, rename batch_use to group_use 2015-03-07 20:59:20 +00:00			`Nested group use statements syntax error`
add tests for batch use declarations with classes, functions and constants 2015-01-19 05:21:11 +00:00			`--FILE--`
			`<?php`
			`namespace Fiz\Biz\Buz {`
require trailing T_NS_SEPARATOR #1005 2015-01-30 22:54:37 +00:00			`use Foo\Bar\Baz\{`
add tests for batch use declarations with classes, functions and constants 2015-01-19 05:21:11 +00:00			`A,`
			`B {`
			`C`
			`D,`
			`E`
			`}`
			`};`
			`}`
			`?>`
			`--EXPECTF--`
Improve output of tokens in Parse Errors Currently, unexpected tokens in the parser are shown as the text found, plus the internal token name, including the notorious "unexpected '::' (T_PAAMAYIM_NEKUDOTAYIM)". This commit replaces that with a more user-friendly format, with two main types of token: * Tokens which always represent the same text are shown like 'unexpected token "::"' and 'expected "::"' * Tokens which have variable text are given a user-friendly name, and show like 'unexpected identifier "foo"', and 'expected identifer'. A few tokens have special cases: * unexpected token """ -> unexpected double-quote mark * unexpected quoted string "'foo'" -> unexpected single-quoted string "foo" * unexpected quoted string ""foo"" -> unexpected double-quoted string "foo" * unexpected illegal character "_" -> unexpected character 0xNN (where _ is almost certainly a control character, and NN is the hexadecimal value of the byte) The \ token has a special case in the implementation just to stop bison making a mess of escaping it and it coming out as \\ 2020-06-11 19:56:22 +00:00			`Parse error: syntax error, unexpected token "{", expecting "}" in %s on line %d`