php-src/Zend/tests/ns_trailing_comma_error_03.phpt

--TEST--
Group use declarations mustn't allow more than one comma
--FILE--
<?php
use Baz\{Foo,,};
?>
--EXPECTF--
Parse error: syntax error, unexpected token ",", expecting "}" in %s on line %d
Add trailing comma syntax support for mixed and unmixed group use lists RFC: https://wiki.php.net/rfc/list-syntax-trailing-commas 2017-04-20 18:08:11 +00:00			`--TEST--`
			`Group use declarations mustn't allow more than one comma`
			`--FILE--`
			`<?php`
			`use Baz\{Foo,,};`
			`?>`
			`--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`