Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:61591 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40773 invoked from network); 20 Jul 2012 23:02:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jul 2012 23:02:55 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:44841] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BF/D1-18983-E93E9005 for ; Fri, 20 Jul 2012 19:02:55 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp16.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 5759A406DF; Fri, 20 Jul 2012 19:02:52 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp16.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 10C3340502; Fri, 20 Jul 2012 19:02:52 -0400 (EDT) Message-ID: <5009E39B.8070803@sugarcrm.com> Date: Fri, 20 Jul 2012 16:02:51 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Laruence CC: PHP Internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Call for voting: [RFC] Allow use T_AS in closure use statement From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Call for voting for "Allow use T_AS in closure use statement", > https://wiki.php.net/rfc/useas#voting > > any comment will be appreciated. I think it would be useful to add some explanation why this change is useful, with specific code examples that it improves. Right now it seems to be lacking good use cases so it's not clear why one would need this - i.e., just renaming the variable doesn't seem all that important... -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227