Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38708
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: php-dev List <internals@lists.php.net>
Message-ID: <3F379336-B4DC-4495-AD76-3D52ED703E0E@pooteeweet.org>
To: Christian Seiler <chris_se@gmx.net>
In-Reply-To: <486B6960.4030705@gmx.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v926)
Date: Wed, 2 Jul 2008 22:18:12 +0200
References: <486B6960.4030705@gmx.net>
Subject: Re: [PHP-DEV] [RFC] Closures: updated proposal and patch
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 02.07.2008, at 13:41, Christian Seiler wrote:

> I've spoken to Dmitry and he said the patch will be committed to HEAD
> soon. Since both Dmitry and I still want to have it in 5_3 too, we'd
> want to ask for opinions on this again - especially since after  
> quite a
> lot of thorough review and discussion on this list basically all the
> side-effects have been addressed and there are now quite a few tests
> that ensure the correct behaviour of closures. Also, the patch is now
> built in a way that the main functionality remains inside
> zend_closures.c, so any possible not yet encountered bug can be fixed
> without breaking binary compability.


I talked to Johannes about this. It does indeed seem like this feature  
is in a very solid stage at this point. However the current version of  
the patch is still young. Also we already have such an insanely long  
list of new big features, that anything that will take even the  
slightest focus away on getting this long list rock solid will have to  
wait until 5.4. Even the most rock solid proposal is bound to have  
some small issues after all.

So as things look atm, closures will have to wait until then. But cool  
features like closures, traits etc will undoubtedly increase the  
incentive to get working quickly on 5.4 and this can happen as soon as  
we have 5.3 out the door and working well for our user base.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org