Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69068 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66428 invoked from network); 11 Sep 2013 21:21:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Sep 2013 21:21:14 -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.100 as permitted sender) X-PHP-List-Original-Sender: bobwei9@hotmail.com X-Host-Fingerprint: 65.55.111.100 blu0-omc2-s25.blu0.hotmail.com Windows 2000 SP4, XP SP1 Received: from [65.55.111.100] ([65.55.111.100:44047] helo=blu0-omc2-s25.blu0.hotmail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 78/10-00307-9CED0325 for ; Wed, 11 Sep 2013 17:21:13 -0400 Received: from BLU0-SMTP120 ([65.55.111.73]) by blu0-omc2-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 11 Sep 2013 14:21:11 -0700 X-TMN: [cpNWIDp55gbhqmOGcm8hazB4WDy367mF] X-Originating-Email: [bobwei9@hotmail.com] Message-ID: Received: from [192.168.178.42] ([188.115.28.77]) by BLU0-SMTP120.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 11 Sep 2013 14:21:07 -0700 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 11 Sep 2013 23:21:05 +0200 To: Developers List PHP Mailing MIME-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) X-Mailer: Apple Mail (2.1508) X-OriginalArrivalTime: 11 Sep 2013 21:21:07.0940 (UTC) FILETIME=[D48B9240:01CEAF34] Subject: Support for keywords where possible From: bobwei9@hotmail.com (Bob Weinand) Hi! 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. 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 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); You can find the patch here: https://github.com/php/php-src/pull/438 Any thoughts about this? Bob Weinand