Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86036
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.18 as permitted sender)
Message-ID: <55415E10.7040908@gmx.de>
Date: Thu, 30 Apr 2015 00:41:20 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
CC: nikic@php.net
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Reserve even more type hints RFC
From: cmbecker69@gmx.de (Christoph Becker)

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).

The "Backward Incompatible Changes" section appears to support my opinion.

[1] <https://wiki.php.net/rfc/reserve_even_more_types_in_php_7>

-- 
Christoph M. Becker