Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77224
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 93.190.64.238 as permitted sender)
Message-ID: <541716F6.5040308@php.net>
Date: Mon, 15 Sep 2014 18:42:30 +0200
Reply-To: internals@lists.php.net
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: internals@lists.php.net
References: <6893A97A-EC4C-4124-B804-96E2A26B953F@ajf.me>
In-Reply-To: <6893A97A-EC4C-4124-B804-96E2A26B953F@ajf.me>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [VOTE][RFC] Scalar Type Hinting with Cast
From: sebastian@php.net (Sebastian Bergmann)

Am 14.09.2014 um 01:30 schrieb Andrea Faulds:
> https://wiki.php.net/rfc/scalar_type_hinting_with_cast

 If I understand the "Syntax" section correctly, then int, float, numeric,
 bool, and string are added as new reserved words (keywords). This would
 break existing code, for instance userland classes named "String".

 However, looking at the patch in http://bit.ly/1uADQnD I do not see
 an addition of new tokens. So maybe there is no problem at all.

 In any case, I think it would be best to build on the great work Nikita
 did with the AST-based parser for PHP 7 and refactor the compiler to
 allow reserved words as names for namespaces, classes, interfaces, ...
 *before* we introduce new reserved words (and thus BC breaks).