Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98173 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52359 invoked from network); 4 Feb 2017 07:41:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Feb 2017 07:41:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=php-lists@koalephant.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=php-lists@koalephant.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain koalephant.com designates 206.123.115.54 as permitted sender) X-PHP-List-Original-Sender: php-lists@koalephant.com X-Host-Fingerprint: 206.123.115.54 mail1.25mail.st Received: from [206.123.115.54] ([206.123.115.54:40564] helo=mail1.25mail.st) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 24/E0-38491-D9585985 for ; Sat, 04 Feb 2017 02:41:17 -0500 Received: from [10.0.1.57] (unknown [183.89.47.214]) by mail1.25mail.st (Postfix) with ESMTPSA id A5ECA6056C; Sat, 4 Feb 2017 07:40:49 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) X-Mailer: iPhone Mail (13G36) In-Reply-To: Date: Sat, 4 Feb 2017 14:40:45 +0700 Cc: Aaron Piotrowski , internals , Ilija Tovilo Content-Transfer-Encoding: quoted-printable Message-ID: <2411D5CB-50B2-4114-8FAD-0513A9A98913@koalephant.com> References: <19.45.38491.677D4985@pb1.pair.com> <611b72db-420f-4963-ab92-0ddf977a0aaa@Spark> <9AF0D2F6-D668-418C-8B96-3320D9D245ED@trowski.com> <5722B01C-A621-4C13-B34B-383B0D9753F9@koalephant.com> <22B18CB2-0383-4D4D-9B55-91A748725AC9@trowski.com> <77287A6A-C3E9-4C93-A1F2-2899DAEA8738@koalephant.com> To: Levi Morrison Subject: Re: [PHP-DEV] [RFC][Discuss] Arrow Functions From: php-lists@koalephant.com (Stephen Reay) On 4 Feb 2017, at 12:26, Levi Morrison wrote: >> So we should instead use syntax already used for bit wise OR, and further= confuse the situation when the function has no parameters and reusing the l= ogical OR operator. Brilliant. >=20 > Excuse me, good sir, but can you tell me what the `&` symbol means? I > thought it meant reference but it's also bitwise and! And when we put > two of them together it is a different kind of and?!?!?! >=20 > Maybe you can tell from the language I used but I don't think your > argument has much merit. Symbol reuse is a problem that programmers > and programming languages have been dealing with for a long time. I > trust us to be able to deal with it, should we agree to go forward > with it. >=20 Your sarcasm is in fact not lost on me my good man, and I do appreciate it. Then surely you agree that there is no issue with function(){...} vs functio= n() =3D> ...being "confusing"? So, is there any argument besides "6 more characters" for *not* using the fu= nction keyword? > --=20 > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >=20