Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:61597 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53765 invoked from network); 21 Jul 2012 00:50:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jul 2012 00:50:21 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.160.42 mail-pb0-f42.google.com Received: from [209.85.160.42] ([209.85.160.42:40733] helo=mail-pb0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0A/54-18983-BCCF9005 for ; Fri, 20 Jul 2012 20:50:20 -0400 Received: by pbbrp12 with SMTP id rp12so7659410pbb.29 for ; Fri, 20 Jul 2012 17:50:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3bb8IjFlbXFeX4HsmiZLIoFOQS5c9tAFAPEyF8R0ov8=; b=AFib/si58tc+7XJYwwRrECIacgj3ly8HsG2RrizTzCQQDzF31IZ7VBfI85KmCK/P6x +ujhBIR3caWizMqyk4wyt7oDPmEGAQHH39JOxv9+dYJQQhI8tp6I+e8fJi+18rsn7Qgw FpAx8miHT9hqVltnoY8k5n4KAQLj2S3i9ehwYJSSf5o+B+z5uD7ANSkrajxrlQho/FfN j5cvcCft/wVYfOz3uCWnU3symAj4J43E37chW/CnLMTig0jx4GPvaqDcDR5EcVX7uNzX bfvw2FelR3XUX39LT/WVz9K4peDVdfMBGK6/5LddhSOvNc6cinkk1T91u7xiLnZLDXEy cQ7w== MIME-Version: 1.0 Received: by 10.68.236.102 with SMTP id ut6mr17800911pbc.113.1342831816751; Fri, 20 Jul 2012 17:50:16 -0700 (PDT) Received: by 10.68.28.41 with HTTP; Fri, 20 Jul 2012 17:50:16 -0700 (PDT) In-Reply-To: <5009E39B.8070803@sugarcrm.com> References: <5009E39B.8070803@sugarcrm.com> Date: Sat, 21 Jul 2012 02:50:16 +0200 Message-ID: To: Stas Malyshev Cc: Laruence , PHP Internals Content-Type: multipart/alternative; boundary=047d7b33d9846e3bb404c54c65e4 Subject: Re: [PHP-DEV] Call for voting: [RFC] Allow use T_AS in closure use statement From: tyra3l@gmail.com (Ferenc Kovacs) --047d7b33d9846e3bb404c54c65e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Jul 21, 2012 at 1:02 AM, Stas Malyshev wrot= e: > 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... > > For starters, maybe we could use a few examples from the previous thread about this rfc: http://www.mail-archive.com/internals@lists.php.net/msg57855.html I really liked the one example from Jordi ( http://www.mail-archive.com/internals@lists.php.net/msg57904.html) --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --047d7b33d9846e3bb404c54c65e4--