Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69111 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 94893 invoked from network); 12 Sep 2013 23:35:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Sep 2013 23:35:04 -0000 Authentication-Results: pb1.pair.com smtp.mail=bobwei9@hotmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=bobwei9@hotmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 65.55.111.103 as permitted sender) X-PHP-List-Original-Sender: bobwei9@hotmail.com X-Host-Fingerprint: 65.55.111.103 blu0-omc2-s28.blu0.hotmail.com Windows 2000 SP4, XP SP1 Received: from [65.55.111.103] ([65.55.111.103:11821] helo=blu0-omc2-s28.blu0.hotmail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D4/93-09838-6AF42325 for ; Thu, 12 Sep 2013 19:35:03 -0400 Received: from BLU0-SMTP457 ([65.55.111.72]) by blu0-omc2-s28.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 12 Sep 2013 16:35:00 -0700 X-TMN: [SFlBWJrKl7cmNsI7Z0n+mGfBQKvMXyV0] X-Originating-Email: [bobwei9@hotmail.com] Message-ID: Received: from [192.168.178.42] ([188.115.28.77]) by BLU0-SMTP457.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 12 Sep 2013 16:34:58 -0700 Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) In-Reply-To: Date: Fri, 13 Sep 2013 01:34:55 +0200 CC: Developers Mailing List PHP Content-Transfer-Encoding: quoted-printable References: <1379018669.12435.1710.camel@guybrush> To: Pierre Joye , Nikita Popov X-Mailer: Apple Mail (2.1508) X-OriginalArrivalTime: 12 Sep 2013 23:34:58.0124 (UTC) FILETIME=[B15228C0:01CEB010] Subject: Re: [PHP-DEV] Support for keywords where possible From: bobwei9@hotmail.com (Bob Weinand) Am 12.9.2013 um 22:59 schrieb Pierre Joye : > On Thu, Sep 12, 2013 at 10:55 PM, Nikita Popov = wrote: >> Supporting different sets of keywords in >> different locations is pretty confusing. Imho we should add this kind = of >> support only in places where a) we can support all keywords and b) it = is >> unlikely that supporting keywords there will cause issues in the = future. a) has the problem while we can now define a class List {} (<=3D allows = all keywords), we cannot access List::const; (<=3D not all keywords are allowed here). (To still access it, it would have to be an uglier = namespace\List::const;) See also https://github.com/php/php-src/pull/438 for which combinations = of keywords are possible. > b) can't be proofed, also the keyword problem being future ready is > also a shiny myth. It is a moving target. They actually aren't future ready for all cases; in my initial mail I = wrote: "Furthermore when BC needs to be broken in future for new keywords, it = will have a __smaller__ impact as __most__ usages of the new keyword then still = work." It will only make the impact smaller; I didn't say that it will make = disappear any impact. > Cheers, > --=20 > Pierre >=20 > @pierrejoye | http://www.libgd.org Bob Weinand=