Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38771 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92003 invoked from network); 4 Jul 2008 17:34:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jul 2008 17:34:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=danielc@analysisandsolutions.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=danielc@analysisandsolutions.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain analysisandsolutions.com from 166.84.1.73 cause and error) X-PHP-List-Original-Sender: danielc@analysisandsolutions.com X-Host-Fingerprint: 166.84.1.73 mail2.panix.com Received: from [166.84.1.73] ([166.84.1.73:50593] helo=mail2.panix.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3C/DF-14155-F3F5E684 for ; Fri, 04 Jul 2008 13:34:57 -0400 Received: from panix3.panix.com (panix3.panix.com [166.84.1.3]) by mail2.panix.com (Postfix) with ESMTP id 5682E34812 for ; Fri, 4 Jul 2008 13:34:53 -0400 (EDT) Received: (from analysis@localhost) by panix3.panix.com (8.11.6p3/8.8.8/PanixN1.1) id m64HYrv18696 for internals@lists.php.net; Fri, 4 Jul 2008 13:34:53 -0400 (EDT) Date: Fri, 4 Jul 2008 13:34:53 -0400 To: PHP Internals List Message-ID: <20080704173453.GB4538@panix.com> References: <486B6960.4030705@gmx.net> <3F379336-B4DC-4495-AD76-3D52ED703E0E@pooteeweet.org> <486C7F5F.3080007@zend.com> <698DE66518E7CA45812BD18E807866CE01C3A902@us-ex1.zend.net> <486D1AD3.3080708@zend.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <486D1AD3.3080708@zend.com> User-Agent: Mutt/1.5.10i Subject: Re: [PHP-DEV] [RFC] Closures: updated proposal and patch From: danielc@analysisandsolutions.com (Daniel Convissor) On Thu, Jul 03, 2008 at 10:30:43PM +0400, Dmitry Stogov wrote: > I don't see big problems with closures. The patch is simple and stable. While you're probably right, it seems there is still lots of discussion about how closures should work. It seems better to get this right in a later version than to jam it in 5.3 just because it will be out sooner. --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409