Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83347 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4006 invoked from network); 20 Feb 2015 19:18:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Feb 2015 19:18:40 -0000 Authentication-Results: pb1.pair.com header.from=dennis@birkholz.biz; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=dennis@birkholz.biz; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain birkholz.biz does not designate 144.76.185.252 as permitted sender) X-PHP-List-Original-Sender: dennis@birkholz.biz X-Host-Fingerprint: 144.76.185.252 mx01.nexxes.net Received: from [144.76.185.252] ([144.76.185.252:43922] helo=mx01.nexxes.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/EE-14173-F2887E45 for ; Fri, 20 Feb 2015 14:17:05 -0500 Received: from [137.226.183.192] (ip3192.saw.rwth-aachen.de [137.226.183.192]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: db220660-p0g-1@packages.nexxes.net) by mx01.nexxes.net (Postfix) with ESMTPSA id 4A127482444 for ; Fri, 20 Feb 2015 20:17:00 +0100 (CET) Message-ID: <54E7882B.30800@birkholz.biz> Date: Fri, 20 Feb 2015 20:16:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: internals@lists.php.net References: <54E7822F.4070307@fischer.name> In-Reply-To: <54E7822F.4070307@fischer.name> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] Reserve EVEN MORE types for PHP7 From: dennis@birkholz.biz (Dennis Birkholz) Am 20.02.2015 um 19:51 schrieb Markus Fischer: > From the RFC: > > “resource” > “object” > “scalar” > “mixed” > “numeric” > > "... prohibits their usage as class, interface and trait names." > > This is such a major BC break. I just wonder why we need to prohibit these names. Can types not reside in the global \ namespace? We could then change the class resolution rules to allow to look also in \ as is done for functions currently. Thanks Dennis