Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86037
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.181 as permitted sender)
Message-ID: <55415FDF.1030204@gmail.com>
Date: Thu, 30 Apr 2015 00:49:03 +0200
User-Agent: Thunderbird
MIME-Version: 1.0
To: internals@lists.php.net
References: <55415E10.7040908@gmx.de>
In-Reply-To: <55415E10.7040908@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Reserve even more type hints RFC
From: keisial@gmail.com (=?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?=)

On 30/04/15 00:41, Christoph Becker wrote:
> Hi everybody!
>
> I've noticed that the "Reserve Even More Types in PHP 7" RFC[1] has been
> moved to "Process and Policy" with the comment "needs no impl".
> However, the RFC states:
>
> | This RFC does not fully reserve them as keywords; it only prohibits
> | their usage as class, interface and trait names.
>
> In my opinion, this has to be enforced by throwing a fatal error
> ("Cannot use '*' as class name as it is reserved"), whenever one of the
> reserved identifiers (resource, object, mixed, numeric) is used as
> class, interface or trait name.
>
> Relying on documentation only seems to be insufficient to me.  Consider
> a developer not reading the documentation and facing the issue that
> his/her code might break with PHP 7.1 (i.e. a minor version).
+1
If not a fatal, it should be at least a warning. Doc-only keyword 
reservation
won't be noticed.