Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98736 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27927 invoked from network); 5 Apr 2017 17:44:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Apr 2017 17:44:10 -0000 Authentication-Results: pb1.pair.com smtp.mail=bjorn.x.larsson@telia.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=bjorn.x.larsson@telia.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.155 cause and error) X-PHP-List-Original-Sender: bjorn.x.larsson@telia.com X-Host-Fingerprint: 81.236.60.155 v-smtpout2.han.skanova.net Received: from [81.236.60.155] ([81.236.60.155:36687] helo=v-smtpout2.han.skanova.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 99/13-08240-2EC25E85 for ; Wed, 05 Apr 2017 13:44:05 -0400 Received: from [192.168.7.8] ([195.198.188.252]) by cmsmtp with SMTP id voyNcRNv5vgExvoyNc713x; Wed, 05 Apr 2017 19:43:59 +0200 To: Rowan Collins References: <97bb5051-6413-b78a-e981-ad8858caec4c@gmail.com> <8d4ee559-1ad2-4d65-ae4f-207e59f056e3@Spark> <61DC1C28-CAF2-45F4-8D9F-A66BEA2E90B1@gmail.com> <3942113e-f83a-444f-bbc2-462c70d67c65@Spark> Cc: Ilja Tovilo , PHP internals Message-ID: <20db9b97-5313-057d-db56-920ccb758558@telia.com> Date: Wed, 5 Apr 2017 19:43:59 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <3942113e-f83a-444f-bbc2-462c70d67c65@Spark> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfGc/IVl4mbMaYnSLIdXdtPW3jtibwJVOYcc/BMNJDhMm3ggUdxJgJHDN+D15UY+dqvTukl/eDNX5k0TDQCS1vu8DhWhpO8lx1hYX8Aukym4bDE4cwcLW i7cv4RgHvyW8QqhLjJW0LkBl/E4SKcMF+n6Z8P+pbklgdh39BfeT859AWdk8iBFNoeZDBwOdHyNs9/GUVZ4UO5MVoZs5GZLDM4OLeo4nNxzc98dT/a3GOdHH OJAhBIg757RAK6N3px/qRg== Subject: Re: [PHP-DEV] [RFC][Discuss] Arrow Functions From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=) Den 2017-03-24 kl. 21:08, skrev ilija.tovilo@me.com: > Hi Rowan > > I see. I still think a simple poll would be useful to choose the least controversial syntax. > Otherwise I fear that the RFC might get rejected out of superficial reasons. > > Regards, > Ilija > > > On 7 Feb 2017, 21:07 +0100, Rowan Collins , wrote: >> Hi Ilija, >> >> On 7 February 2017 18:58:15 GMT+00:00, ilija.tovilo@me.com wrote: >>> And also, have you considered letting people vote for their preferred >>> arrow function syntax? >>> I kinda don’t think we’re gonna find an agreement as there are so many >>> different opinions. >> The problem with voting on alternative syntaxes is precisely that there *are* so many different options. Designing a vote with multiple options that gives an answer people are happy with is a whole science in itself. >> >> I think the best we can do is have a "without prejudice" vote on a single proposal - if it is declined, a new proposal can be made after a suitable period of reflection. This has already happened once with this very topic, this RFC having emerged from a previous one being rejected. >> >> That doesn't mean we can't discuss other syntaxes, but just opening up all possible options to a vote doesn't really help IMHO. >> >> Regards, >> >> -- >> Rowan Collins >> [IMSoP] >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> Hi, My suggestion for a vote would be: - Vote about the feature. - Vote about syntax if no consensus can be reached. My suggestion would be to both have a short and long version: - |params| => expr - lambda(params) => expr An example where one have two syntaxes for same feature is the jQuery library, i.e. $() and jQuery(). I plan to read up on the RFC once more this week regarding the feature itself. Any plans to go with this for 7.2? Regards //Björn Larsson