Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87783
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.19 as permitted sender)
To: Arne Blankerts <theseer@netpirates.net>,
 "internals@lists.php.net" <internals@lists.php.net>
References: <1439930857.5060.18.camel@netpirates.net>
Message-ID: <55D3AF40.4080209@gmx.de>
Date: Wed, 19 Aug 2015 00:18:40 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <1439930857.5060.18.camel@netpirates.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: Syntactical inconsistency with new group use syntax
From: cmbecker69@gmx.de (Christoph Becker)

On 18.08.2015 at 22:47, Arne Blankerts wrote:

> while playing around with the new group use syntax, I stumbled upon an
> inconsistency of which I'm not sure whether or not it is expected.
> For the "classic" syntax, while technically pointless, a leading \ for
> the name is considered valid and works identical to a line without it:
> 
> <?php
> 
> namespace foo;
> 
> use \some\bar;
> use some\baz;
> 
> 
> With the new group syntax, the version with a leading \ is considered
> invalid - a lint will PHP Parse error: syntax error, unexpected '{',
> expecting identifier (T_STRING):
> 
> <?php
> 
> namespace foo;
> use some\{ bar, baz };
> use \some\{ bar, baz };
> 
> 
> 
> 
> Is this a bug or feature?

It seems to me that is an oversight.  The resolution would be rather
simple, cf.
<https://github.com/php/php-src/blob/php-7.0.0beta3/Zend/zend_language_parser.y#L366-L375>.

However, while looking at the grammar, I've noticed that the entities
inside the braces may start with a backslash, what I consider rather
strange (particularly as there has to be a backslash immediately before
the opening brace).

-- 
Christoph M. Becker