Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38362 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1224 invoked from network); 18 Jun 2008 19:59:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jun 2008 19:59:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=indeyets@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=indeyets@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.46.30 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: indeyets@gmail.com X-Host-Fingerprint: 74.125.46.30 yw-out-2324.google.com Received: from [74.125.46.30] ([74.125.46.30:15883] helo=yw-out-2324.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BF/33-03518-73969584 for ; Wed, 18 Jun 2008 15:59:51 -0400 Received: by yw-out-2324.google.com with SMTP id 5so226556ywb.83 for ; Wed, 18 Jun 2008 12:59:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=K3CcylLKo3kS6zkcWiho6u1prBFao6yHQHVqk5Me5dw=; b=nvOGXNAr0kBxOp+yhfU5yTx9N7srZclwcIVBcBm4TUcyUY7odgg3Nz8+Dfv1P+Txgu 0APXqRcgl6xFM1/IMYQ1OQAi9Eq8cMwS+fTzl7sGMKpMkKufXpSdcyyYc3P6Q3XmcpXn o4v62RgGPtduJFekdBEoM1C3VYUbBxPtZ7qxo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=DYFEQMk8Jb1NdXBdl0Sg+UUB8ABM3pENI3OVy44SmOIqO+da5GoEIfODxYses1ch8F Wr0Lto/2sAk/U4h8IVf6P6zNIPP23uRLVvoxbQSBh4NTx2FlvCE/uYSecuYG9F0GBikl Z1K7ewgtLTamZaKR2wcO1N4C/q+gayDQqNAc4= Received: by 10.150.136.6 with SMTP id j6mr1657049ybd.139.1213819188926; Wed, 18 Jun 2008 12:59:48 -0700 (PDT) Received: by 10.150.158.8 with HTTP; Wed, 18 Jun 2008 12:59:48 -0700 (PDT) Message-ID: Date: Wed, 18 Jun 2008 23:59:48 +0400 To: "Stanislav Malyshev" Cc: "Andi Gutmans" , "Christian Seiler" , "php-dev List" In-Reply-To: <485953F5.1070602@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4856A547.3080801@gmx.net> <698DE66518E7CA45812BD18E807866CE01B11811@us-ex1.zend.net> <4858FCC7.5030305@gmx.net> <698DE66518E7CA45812BD18E807866CE01B70D73@us-ex1.zend.net> <485953F5.1070602@zend.com> Subject: Re: [PHP-DEV] [PATCH] [RFC] Closures and lambda functions in PHP From: indeyets@gmail.com ("Alexey Zakhlestin") On 6/18/08, Stanislav Malyshev wrote: > Which brings me to another point - how bad would it be if closure's > lifetime would be limited to parent's lifetime? Of course, this would limit > some tricks, but would allow some other - like this direct access to > parent's scope. that would be seriously bad, because it will eliminate possibility of lambda-generating functions -- Alexey Zakhlestin http://blog.milkfarmsoft.com/