Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87781
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1439930857.5060.18.camel@netpirates.net>
References: <1439930857.5060.18.camel@netpirates.net>
Date: Tue, 18 Aug 2015 19:14:24 -0300
Message-ID: <CAOsHV+toWJ20su8VpRxhRVMEuz8_oPZkSmeUO-kQ_Drr-GgRBw@mail.gmail.com>
To: Arne Blankerts <theseer@netpirates.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Syntactical inconsistency with new group use syntax
From: marcio.web2@gmail.com (Marcio Almada)

Hi,

2015-08-18 17:47 GMT-03:00 Arne Blankerts <theseer@netpirates.net>:
> Hi everyone,
>
> 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?
>
> Regards,
>    Arne
>
> --
> Those who do not understand Unix
>       are condemned to reinvent it, poorly (Henry Spencer,1987)
>

This is definitely a bug. The leading slash is part of the main
namespace spec and therefore should be respected. This should have
been more explicit in the RFC.

I'll send a pull request with a fix.

Thanks,
M=C3=A1rcio Almada