Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69593 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61887 invoked from network); 16 Oct 2013 21:45:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Oct 2013 21:45:58 -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.83 as permitted sender) X-PHP-List-Original-Sender: bobwei9@hotmail.com X-Host-Fingerprint: 65.55.111.83 blu0-omc2-s8.blu0.hotmail.com Windows 2000 SP4, XP SP1 Received: from [65.55.111.83] ([65.55.111.83:5337] helo=blu0-omc2-s8.blu0.hotmail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 36/20-60229-4190F525 for ; Wed, 16 Oct 2013 17:45:56 -0400 Received: from BLU0-SMTP82 ([65.55.111.71]) by blu0-omc2-s8.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 16 Oct 2013 14:45:58 -0700 X-TMN: [0JC2Hf0zbAg4HEp8yv6racESGXqEhQ5n] X-Originating-Email: [bobwei9@hotmail.com] Message-ID: Received: from bob-weinands-imac.fritz.box ([188.115.61.21]) by BLU0-SMTP82.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 16 Oct 2013 14:45:55 -0700 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) In-Reply-To: Date: Wed, 16 Oct 2013 23:45:46 +0200 Content-Transfer-Encoding: quoted-printable References: To: Developers List PHP Mailing X-Mailer: Apple Mail (2.1510) X-OriginalArrivalTime: 16 Oct 2013 21:45:56.0035 (UTC) FILETIME=[17FA1930:01CECAB9] Subject: Re: [PHP-DEV] Support for keywords where possible From: bobwei9@hotmail.com (Bob Weinand) I plan to move this rfc forward to voting phase in the next days. I have made some (huge) changes to the initial implementation over the = last weeks. There initially was the problem that there were some ugly restrictions = which keywords are allowed under which circumstances. They are now resolved (=3D all keywords possible except the ones which = conflict with existing functionality). If there aren't any further objections now, I'll move it to voting = phase. Bob Weinand Am 11.9.2013 um 23:21 schrieb Bob Weinand : > Hi! >=20 > I tried to widen the naming possibilities by allowing to use keywords = as identifiers (for function names, class names, label (goto) names, = ...) where possible. It doesn't break any BC. >=20 > 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. >=20 > It also prevents unnecessary workarounds like in = https://wiki.php.net/rfc/named_params#syntax. There, to address a = function with a parameter called $array, we could simply write = func(array =3D> $value); instead of the until now necessary func("array" = =3D> value); >=20 > You can find the patch here: > https://github.com/php/php-src/pull/438 >=20 > Any thoughts about this? >=20 > Bob Weinand