Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54352 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72311 invoked from network); 4 Aug 2011 12:27:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Aug 2011 12:27:26 -0000 Authentication-Results: pb1.pair.com header.from=arvids.godjuks@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=arvids.godjuks@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender) X-PHP-List-Original-Sender: arvids.godjuks@gmail.com X-Host-Fingerprint: 209.85.220.170 mail-vx0-f170.google.com Received: from [209.85.220.170] ([209.85.220.170:51777] helo=mail-vx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 84/79-18399-C209A3E4 for ; Thu, 04 Aug 2011 08:27:25 -0400 Received: by vxh24 with SMTP id 24so309642vxh.29 for ; Thu, 04 Aug 2011 05:27:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XV3PHU0iz/doF4S5olSLLhYfKR4JExDoft1h9JXCY3M=; b=V8LEbWKtu9hC6VG0fTXyRypHknTyF5ZHM+DYMyDQXvJd8Wd65hxnQt3Kg8aV8yheHq mcN/oKAg9EdTt2IaYdxWKHMAw0EZ+wTSMudWTDW3nLx/VyY76GSvxw7BVBWHB/GAHycB NLm4A78+SI2qtVq7Ngk/PKVCyyZ6S8sOgeTxo= MIME-Version: 1.0 Received: by 10.52.91.79 with SMTP id cc15mr744339vdb.284.1312460841815; Thu, 04 Aug 2011 05:27:21 -0700 (PDT) Received: by 10.52.185.41 with HTTP; Thu, 4 Aug 2011 05:27:21 -0700 (PDT) In-Reply-To: References: Date: Thu, 4 Aug 2011 15:27:21 +0300 Message-ID: To: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] An implementation of a short syntax for closures From: arvids.godjuks@gmail.com (Arvids Godjuks) Oh, and I forgot one more thing: As I read the internals, I noticed many times that PHP lexer is somewhat limited in it's capabilities and sometimes the features are dropped because of this issue. It can be the case that the can be ambiguous and it will be just impossible to add at this stage. As Ryan McCue pointed out in his example - there can be a problem with arrays. And so on. Use cases are not just limited to declaring a lambda as a function callback or assigning it to a variable. Creatinx syntax that just looks odd for the language like those | probably will not be accepted by the community because it looks out of place. my 2 cents